| clarifying the importance of includes & requires in feature.xml for <eclipse.generateBuildScr [message #39282] |
Tue, 06 January 2009 21:56 |
 Nicolas Rouquette
Messages: 157
Registered: July 2009 |
Senior Member |
|
|
I spent a couple of days tracking a mysterious build problem for a
product P that includes two features, A and B where A includes B.
<feature id="A" ...>
<includes id="B" .../>
...
</feature>
The PDE log for building P failed with annoying compilation errors:
import x.y.z.Foo;
^^^^^
The import x.y.z cannot be resolved.
Examining the build artifacts, I realized that the generated build
script led to building A before B. Since the generated build.xml script
includes classpath elements that refer to the binary folder of the
plugin, the compilation of the plugins for feature A failed simply
because the binary folders for the B plugins had yet to be created!
Fixing this was simple:
<feature id="A" ...>
<includes id="B" .../>
<requires>
<import feature="B" .../>
...
</requires>
...
</feature>
Since the feature editor does not allow us to change the order in which
features are included in a feature.xml file, it seems rather important
to verify that dependencies among features are explicitly defined in the
feature.xml instead of relying on luck that they will be built serially
in the order that they are included.
This point seems even more important in consideration of the fact that
one could take advantage of new support for concurrent builds in PDE to
speed up continuous builds.
Comments?
Regards,
-- Nicolas.
|
|
|
Powered by
FUDForum. Page generated in 0.03441 seconds
] 
Search
Help
Register
Login
Home
