>>>>> Steinar Bang <[EMAIL PROTECTED]>:

>> I've succeeded in building my eclipse RCP app (developed against eclipse
>> 3.2.2) with eclipse 3.3.2, by forcing the newest pde-maven-plugin
>> snapshot (this fixed the "missing startup.jar" problem).

>> But now I'm unable to build my app against eclipse 3.2.2.  I get this
>> line at the end:
>> /home/sb/p4/depot/myapp/MAIN/myapp_eclipse_studio_export/myapp_studio_win32/assemble.org.eclipse.pde.build.container.feature.win32.win32.x86.xml:126:
>>  java.io.EOFException

I've figured out what the problem was.  I build RCP applications with
maven, using the following pattern:
 - there's a top POM that runs the entire build process as a
   multi-project
 - the child projects are:
  - A project that zips up the plug-in sources from their perforce
    workspace 
  - A project that matches source and configuration to fit the
    pde-maven-plugin projects
  - A project that builds the PDE target platform
  - A pde-maven-plugin super POM that sets common values for the
    pde-maven-plugin and runs the different platform builds

The project that was still built with eclipse 3.2.2 was added as a child
of the pde-maven-plugin super POM, and values overriden, as well as
getting its own separate PDE target platform, built as its own child
project (and depending on it, to get the right build order).

My problem was caused by that the PDE target platform was being
specified in two places in the pde-maven-plugin super POM, and 
that I had only overridden one of them in the 3.2.2 based child POM.

The configuration in the child now looks like this:
    <plugin>
     <groupId>org.codehaus.mojo</groupId>
     <artifactId>pde-maven-plugin</artifactId>
     <extensions>true</extensions>
     <configuration>
      <pdeBuildVersion>3.2.1.r321_v20060823</pdeBuildVersion>
      
<eclipseInstall>${basedir}/eclipse_pde_target_platform/target/eclipse</eclipseInstall>
      <buildProperties>
       
<baseLocation>${basedir}/eclipse_pde_target_platform/target/eclipse</baseLocation>
      </buildProperties>
     </configuration>
     ...

When I only overrode the <eclipseInstall> setting, I got the above error
message.  When I added <buildProperties><baseLocation/></buildProperties>
it built successfully.

With only <eclipseInstall> set, the correct target platform was used for
the pde:clean-pde goal, while the pde:build-pde goal used the
<baseLocation> setting of the parent (which is currently based on
eclipse 3.3.2).



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to