|Re: how to debug unresolved dependencies in PDE build [message #634480 is a reply to message #634475]
||Thu, 21 October 2010 20:58
| Laurent Marchal
Registered: July 2009
I guess you are using a -feature based- product, so you don't have a
button "add required plugins" to easily compute the required dependencies..
I have the same kind of project and it's a nightmare to know the needed
dependencies and add them manually ! But I have a trick I found after
hours of playing with those dependencies / build..
What I do is
* Open the product file
* Click on "Launch an eclipse application" (this will create a launch
configuration synchronized with your product definition)
* Edit this launch configuration and check "validate plugins prior to
* Now every time you update one of your features, just click on "Launch
an eclipse application" again and if you have unmet dependencies eclipse
will display them.
You can now fix all the needed dependencies. Then if your project run
fine in eclipse, the build should work too.
Le 10/21/2010 03:33 PM, Jon Svede a écrit :
> I have a product build based on 3.5 running in Hudson. The product is
> features based. The build ran fine until I added a new plugin to my
> target platform.
> I updated my product definition, the target definition and all the
> features that require this new plugin. My product export is working fine
> in the IDE. However, nothing I do seems to fix this issue in the build.
> I keep getting the following:
> [java] generateFeature:
> [java] [eclipse.buildScript] Bundle org.myclient.app.editor:
> [java] [eclipse.buildScript] Missing required plug-in
> And then the build fails. There are other messages in this output, but
> they have been there for a while and have never affected the success of
> the build.
> Is there a way to turn on additional debugging in the build that will
> give me a better idea of why it's failing?
> In this case, the plugin org.myclient.app.editor has the dependency
> properly listed in dependency tab of the manifest. Additionally, it's
> also enumerated as a dependency in the feature.xml that this plugin is a
> part of (on both the plug-ins and dependencies tabs) as well as the
> parent feature of this feature. I am out of ideas of where else I need
> to specify this dependency.
> Thanks in advance.
Powered by FUDForum
. Page generated in 0.30828 seconds