| Headless PDE build problem [message #8314] |
Tue, 24 June 2008 09:19  |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
I have a set of plugins that won't build now that I've introduced a
dependency between them. PluginA and PluginB have each been building
fine for a couple of weeks. Yesterday I introduced a dependency from
PluginB on PluginA (B uses classes in A) and now the PDE build complains
when trying to build PluginB that it can't find the classes in PluginA.
I've checked and the source code for PluginA is sitting right there in
the working directory next to the source for PluginB, and the manifest
for PluginB correctly lists PluginA as a required bundle.
It seems as if it's trying to build PluginB before PluginA, even though
the dependency means PluginA has to be built first. How does PDE Build
determine the order in which to build plugins?
Everything compiles successfully in Eclipse, of course.
Where do I start to track down the problem?
TIA,
Eric
|
|
|
| Re: Headless PDE build problem [message #8346 is a reply to message #8314] |
Tue, 24 June 2008 10:25  |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Just FYI for anyone who stumbles on this thread later: the problem was
that I had forgotten to add PluginA to the feature.xml and thus PDE
Build didn't "know" about it.
Eric
Eric Rizzo wrote:
> I have a set of plugins that won't build now that I've introduced a
> dependency between them. PluginA and PluginB have each been building
> fine for a couple of weeks. Yesterday I introduced a dependency from
> PluginB on PluginA (B uses classes in A) and now the PDE build complains
> when trying to build PluginB that it can't find the classes in PluginA.
> I've checked and the source code for PluginA is sitting right there in
> the working directory next to the source for PluginB, and the manifest
> for PluginB correctly lists PluginA as a required bundle.
> It seems as if it's trying to build PluginB before PluginA, even though
> the dependency means PluginA has to be built first. How does PDE Build
> determine the order in which to build plugins?
>
> Everything compiles successfully in Eclipse, of course.
>
> Where do I start to track down the problem?
>
> TIA,
> Eric
|
|
|
| Re: Headless PDE build problem [message #569976 is a reply to message #8314] |
Tue, 24 June 2008 10:25 |
| Eclipse User |
|
|
|
Just FYI for anyone who stumbles on this thread later: the problem was
that I had forgotten to add PluginA to the feature.xml and thus PDE
Build didn't "know" about it.
Eric
Eric Rizzo wrote:
> I have a set of plugins that won't build now that I've introduced a
> dependency between them. PluginA and PluginB have each been building
> fine for a couple of weeks. Yesterday I introduced a dependency from
> PluginB on PluginA (B uses classes in A) and now the PDE build complains
> when trying to build PluginB that it can't find the classes in PluginA.
> I've checked and the source code for PluginA is sitting right there in
> the working directory next to the source for PluginB, and the manifest
> for PluginB correctly lists PluginA as a required bundle.
> It seems as if it's trying to build PluginB before PluginA, even though
> the dependency means PluginA has to be built first. How does PDE Build
> determine the order in which to build plugins?
>
> Everything compiles successfully in Eclipse, of course.
>
> Where do I start to track down the problem?
>
> TIA,
> Eric
|
|
|
Powered by
FUDForum. Page generated in 0.04101 seconds
Home