Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » Headless PDE build problem
Headless PDE build problem [message #8314] Tue, 24 June 2008 13:19 Go to next message
Eclipse UserFriend
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 14:25 Go to previous message
Eclipse UserFriend
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 14:25 Go to previous message
Eric Rizzo is currently offline Eric RizzoFriend
Messages: 3070
Registered: July 2009
Senior Member
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
Previous Topic:Headless PDE build problem
Next Topic:Classpath entries for Plugin unit test
Goto Forum:
  


Current Time: Sat Sep 21 01:34:38 GMT 2024

Powered by FUDForum. Page generated in 0.04238 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top