| Question about a Feature Dependencies "Compute" function [message #554300] |
Sat, 21 August 2010 02:24  |
|
I have two plugins, A & B. Plugin-A has a Require-Bundle dependency on
Plugin-B. I also have a feature that has "<plugin>" entries for both
plugins A & B. When I use the "Compute" button on the Dependencies tab of
the feature, it adds a "<requires><import plugin>" (Dependencies tab)
entry for Plugin-B. Is this correct?
Our build guy who set up our P2 builds on Hudson was surprised to hear
this and stated he actually has code in his build scripts that throws an
error when a plugin is listed in both the "<plugin>" and
"<requires><import plugin>" sections of a feature. I manually removed the
"<requires><import plugin>" entry for Plugin-B and the build worked fine.
His thinking I believe is that "<plugin>" entries indicate "build me"
whereas "<requires><import plugin>" (Dependencies tab) entries indicate
"find me as a P2 artifact, one of the <plugin> entries being built
depends on me". If that's correct, the build should not be looking for a
previous build of Plugin-B but rather the current build of Plugin-B
should be used to satisfy Plugin-A's dependency.
When it's put that way, I have to wonder if the "Compute" function added
the "<requires><import plugin>" entry for Plugin-B because I don't have
my dependencies set correctly somewhere.
What would you expect "Compute" to do in this situation? Any help greatly
appreciated.
Craig
|
|
|
 Re: Question about a Feature Dependencies "Compute" function [message #554926 is a reply to message #554300] |
Tue, 24 August 2010 18:40  |
|
Anyone? Is there a problem with the question? Is this not the correct group?
I'll attempt to rephrase:
If I have two plugins, one dependent on the other, included in a feature, the Compute button on the feature's Dependency tab lists the plugin depended upon as a dependency. Why?
Doesn't this indicate the plugin is a dependency of the feature build when in fact it isn't? I want the building of the feature to build both plugins, presumably the one depended upon first.
I suspect the button's behaviour is correct, I'm just not sure what it's indicating and how it's used in the feature build.
Again, any help greatly appreciated.
Craig
[Updated on: Tue, 24 August 2010 18:52] Report message to a moderator |
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03178 seconds
] 
Search
Help
Register
Login
Home
