| dynamic dependencies [message #640589] |
Mon, 22 November 2010 14:52 |
 Jesper Eskilson
Messages: 134
Registered: July 2009 |
Senior Member |
|
|
I'm building two p2 sites, call them A and B. The only difference
between them is that B of them contains two fragments, B1 and B2, which
should not be included in A. My build script looks like this:
resolve A.cquery
resolve B.cquery
build
perform A#site.p2
perform B#site.p2
The cqueries work correctly as I can see; A.cquery resolves all plugins
which should go into the A site, and B.cquery resolves to B1 and B2 to
be included in the B site.
The problem here is that when Buckminster builds the A site, it included
the B1 and B2 fragments as well. Running Buckminster with DEBUG output
shows the following output
[java] Project ...B1... now has dynamic dependencies to ...project
in A...
[java] Project ...B2... now has dynamic dependencies to ...project
in A...
Googling on "eclipse p2 dynamic dependencies" refers me to
http://wiki.eclipse.org/Equinox_p2_1.0_Features where I can read
Dynamic dependency discovery
When p2 is asked to install an IU it can optionally attempt to satisfy
all prerequisites by discovering and installing other IUs that supply
the required capabilities. Priority: 2
Am I correct in assuming that it is the dynamic dependency discovery
which is causing the B1 and B2 fragments to be included in the A site,
and if so, how can I prevent them from being included?
--
Jesper Eskilson
Developer
IAR Systems
|
|
|
Powered by
FUDForum. Page generated in 0.01907 seconds
] 
Search
Help
Register
Login
Home
