[Rifidi-developers] TargetPlatform and eclipse 3.4 vs 3.5

[Rifidi-Developers L. <rif...@li...>]

The target platform editor in 3.5 produces target platform files that 
are not backward compatible with the target platform editor in 3.4.  We 
need to decide if we are "officially" upgrading to 3.5 as a development 
environment.

3.5 target platform files:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?pde version="3.5"?>

<target>
<locations>
<location path="${workspace_loc}/org.rifidi.edge.target" type="Profile"/>
<location path="${workspace_loc}/org.rifidi.edge.target/esper" 
type="Directory"/>
<location path="${workspace_loc}/org.rifidi.edge.target/spring" 
type="Directory"/>
<location path="${workspace_loc}/org.rifidi.edge.target/libraries" 
type="Directory"/>
<location path="${workspace_loc}/org.rifidi.edge.target/aspectj" 
type="Directory"/>
<location path="${workspace_loc}/org.rifidi.edge.target/eclipseaspects" 
type="Directory"/>
</locations>
</target>


3.4 target platform files:
<?xml version="1.0" encoding="UTF-8"?>
<?pde version="3.2"?>

<target>

   <location path="${workspace_loc}/org.rifidi.edge.target"/>

   <content useAllPlugins="true">
      <plugins>
      </plugins>
      <features>
      </features>
      <extraLocations>
         <location path="${workspace_loc}/org.rifidi.edge.target/esper"/>
         <location path="${workspace_loc}/org.rifidi.edge.target/spring"/>
         <location 
path="${workspace_loc}/org.rifidi.edge.target/libraries"/>
      </extraLocations>
   </content>

</target>


-Kyle