<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<plugin
   id="org.eclipse.hyades.execution.local"
   name="Hyades Execution Local"
   provider-name="Eclipse.org"
   version="3.0.1">

   <runtime>
      <library name="hexl.jar">
         <export name="*"/>
      </library>
   </runtime>
   <requires>
      <import plugin="org.eclipse.hyades.execution.core" export="true"/>
      <import plugin="org.eclipse.core.runtime"/>
      
      
<!-- ================================================================= -->
<!-- There is no mechanism in the build right now to dynamically plug  -->
<!-- security providers into the driver in such a means that the       -->
<!-- classloader will be able to resolve the classes at runtime. when  -->
<!-- running JRE's that pre-date java 1.4.  This an example of how to  -->
<!-- achieve this on JRE's prior to Java 1.4 when the JSSE provider is -->
<!-- not installed ine th JVM.  With Java 1.4 JRE the JSSE classes     -->
<!-- be resolved providing the JSSE provider classes are in the        -->
<!-- classpath of the plugin providing the extension class desribing   -->
<!-- the JSSE provider.  In this example the JSSE provider is in the   -->
<!-- com.ibm.etools.jsse plugin and it is optional so that it can be   -->
<!-- located at runtime but if it is not, security will not work. Of   -->
<!-- course, you can                                                   -->
<!-- avoid the entire classpath problem if you install the JSSE with   -->
<!-- the JVM.                                                          -->
<!-- ================================================================= -->        
      <import plugin="com.ibm.etools.jsse" optional="true"/>
   </requires>

</plugin>
