Re: [pde-build-dev] eclipse.buildScript: Requires features to be in "fea

["Pascal Rapicault" <Pascal_Rapicault@xxxxxxxxxx>]

Martin, 

The pde-build mechanism went under a major reorganisation, and as a consequence you should be able to do what you need using 3.0 drops from M2.
It will allow you to really easily do all what you need to do: it provides functionnality to create links and move files around and comes with reusable scripts.
It is the mechanism used to build the eclipse drops.

You can find examples in the project org.eclips.releng.eclipsebuilder (available from CVS), as well as in the plugin org.eclipse.pde.build_3.0.0/feature/builder

HTH
        PaScaL

"Martin Buechi" <Martin.Buechi@xxxxxxxxxxxxxxx> Sent by: pde-build-dev-admin@xxxxxxxxxxx 08/21/2003 11:21 AM Please respond to pde-build-dev

To:        <pde-build-dev@xxxxxxxxxxx>         cc:                 Subject:        [pde-build-dev] eclipse.buildScript: Requires features to be in "features" folder

All,

I would like to use the eclipse.buildScript task to create ant build files
for features and their plugin children from within Eclipse 2.1.1. However,
it seems that this task only works if the feature is in a folder features
(org.eclipse.pde.internal.build.IPDEBuildConstants.DEFAULT_FEATURE_LOCATION)
because the ant task does not let me specify the featureRootLocation. The
latter is set explicitly from the popup menu "Create Ant Build File." Is my
assessment correct or am I overlooking something?

To be more precise, here is my layout on disk:

eclipse
workspace
com.foo.feature    // feature project
com.foo.plugin1    // plugin project
com.foo.plugin2    // plugin project
com.foo.build      // simple project
mybuild.xml  // hand-written build file


In the hand-created mybuild.xml file, I would like to create an Eclipse
product using the following steps:

1. Use eclipse.buildScript to create the build.xml scripts for all the
features and their children. (This is the step where I fail.)

2. Use the build.xml scripts to build the features.

3. Manually move the startup.jar and splash.bmp from org.eclipse.platform.

4. Zip it up.

A symbolic link may work in eclipse that aliases workspace with features may
help, but this wouldn't be portable.

Is there a good way to do this? Is there a better overall approach that
works from within Eclipse 2.1.1?

Regards,

Martin

P.S.        I am posting here rather than on platform-releng-dev because the
code is in org.eclipse.pde.





#### Martin Buechi, Ph.D..vcf has been removed from this note on August 21, 2003 by Pascal Rapicault