Re: [pde-build-dev] Order of compiling plugins during headless build
• From: Felix Zielke <felix.zielke@xxxxxxxxxxxxxxxxxx>
• Date: Fri, 07 Dec 2007 10:22:04 +0100
• Delivered-to: pde-build-dev@eclipse.org
• Organization: Fraunhofer-Institut für Intelligente Analyse- und Informationssysteme
• User-agent: Thunderbird 2.0.0.9 (Windows/20071031)

Someone gave me a tip and I tried it out:
- Define a root feature that contains the plug-in for the product branding
- Put other plug-ins in features and include these features in the the root feature
- Important: Edit the root feature's feature.xml manually by putting the feature includes in the correct order (put features that contain plug-ins depending on other features' plug-ins below the independent features)

It's working like that. Might this be a bug in PDE build tools? I guess it should be able to compute the dependencies automatically.

```Thanks,
Felix```

Marshall Harnish schrieb:
Unfortunately, I don't know of a way to influence the build order manually...

The way I found out it was building them in the correct order was to add custom build xml files to each plugin, which get called by the PDE builder during the build process. Then, I examined the order of the calls Ant was making. You could try something similar to see if it is actually trying to build your plugins out of order, or if there is some other problem.

Actually, another problem that I had during the build process was that I was trying to build one of the plugins as a directory, not a jar file. To do this in Eclipse, your plugin's build include path (bin.includes line in the manifest file) must not contain an entry for the '.' character. PDE Builder was doing the wrong thing in this case and not moving the generated class files to the correct directory, resulting in a similar problem. If you are deploying your plugin as a directory, that might be the case as well.

` - Marshall`

------------------------------------------------------------------------
> Date: Thu, 6 Dec 2007 09:09:17 +0100
> From: felix.zielke@xxxxxxxxxxxxxxxxxx
> To: pde-build-dev@xxxxxxxxxxx
> Subject: Re: [pde-build-dev] Order of compiling plugins during headless build
>
> Hi Marshall,
>
> all my plugins have the
> source.. = src/
> output.. = bin/
> entries, so this can't be the problem.
> > I was having the same problem with the PDE build for a product I was
> > working on. It turns out that the PDE Builder was calculating the
> > plugin order correctly,
> How did you know that? Do I have to influence the build order manually?
>
> Felix
> > however, I didn't have a 'source..' entry in my build.properties
> > file. This was causing the PDE builder not to compile the plugin's
> > class files.
> >
> > Make sure that the plugin's build.properties has the source.. and
> > output.. entries defined correctly.
> >
> > - Marshall
> >
> >
> >
> > ------------------------------------------------------------------------
> > > Date: Wed, 5 Dec 2007 13:41:38 +0100
> > > From: felix.zielke@xxxxxxxxxxxxxxxxxx
> > > To: pde-build-dev@xxxxxxxxxxx
> > > Subject: [pde-build-dev] Order of compiling plugins during headless
> > build
> > >
> > > Hello,
> > >
> > > we are doing a headless product build for our rcp application and we
> > > encoutered the following problem: the plugins are compiled in the wrong
> > > order means the headless build does not follow the dependencies as
> > > defined in the "plugin.xml"s.
> > >
> > > Here is the situation: We have a product which contains one feature. In
> > > that feature are the plugins pluginA, pluginB and pluginC (in fact
> > there
> > > are 10 plug-ins, but I simplify it here). PluginB depends on pluginA
> > and
> > > pluginC. During the headless product build the ant script from the pde
> > > tools builds first pluginA and then pluginB. That is the point where I
> > > get the error because pluginB cannot find the packages of pluginC.
> > If we
> > > are using the Export product wizard from the Eclipse IDE, everything
> > > works fine.
> > >
> > > The error I get is
> > > 1. ERROR in C:\xyz\build\plugins\pluginB\src\Example.java (at line 32)
> > > import org.example.package.ExampleClass;
> > > ^^^^^^^^^^^^^^^^
> > > The import org.example.package cannot be resolved
> > >
> > > I hope the problem became clear, thanks for your help.
> > >
> > > Greets,
> > > Felix
> >
> > ------------------------------------------------------------------------
> > Get the power of Windows + Web with the new Windows Live. Power up!
> > <http://www.windowslive.com?ocid=TXT_TAGLM_Wave2_powerofwindows_112007>
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > pde-build-dev mailing list
> > pde-build-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/pde-build-dev
> >

------------------------------------------------------------------------
You keep typing, we keep giving. Download Messenger and join the i’m Initiative now. Join in! <http://im.live.com/messenger/im/home/?source=CRM_WL_joinnow>
------------------------------------------------------------------------

_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev
```begin:vcard
fn:Felix Zielke
n:Zielke;Felix
org:Fraunhofer-Institut Intelligente Analyse- und Informationssysteme;Competence Center NetMedia