Clarification, unchecking the box should not "grab all dependencies". It will follow the feature *include* dependencies and get the specific versions listed therein, ignoring those that cannot be found.
Jeff
On 2010-04-22, at 3:20 PM, Curtis Windatt wrote: Hi Eric,
Yes, this is expected behaviour. The
target resolves the required dependencies of each location independently.
If you want to create a target from multiple sites you can uncheck
the "Include required software" button at the bottom of the Add
Content from Software Site wizard. When trying to gather requirements,
the site will (using the p2 slicer) grab all dependencies that are available
in the repo you are working with and will ignore dependencies it cannot
find.
Curtis
Hi,
I've been trying to figure out a weird issue I've been getting trying to
create a Target platform from an update site.
Basically the issue appears to be that when creating a Target Platform,
P2 does not look outside the selected repo to resolve dependencies. If
the Helios repo is used everything resolves fine. If the local project
repo is used there are errors that required dependencies are missing -
Even if the default platform is used as a starting point (so the
platform isn't used to resolve dependencies either).
Is this expected behavior?
Anyone?
--
-Eric
Oracle <http://www.oracle.com>
Eric Gwin | Senior Software Developer
Phone: +613 288 4622 <tel:+613%20288%204622> | | Fax: +613 2382818
<fax:+613%202382818> | | Mobile: +613 8582347 <tel:+613%208582347>
Oracle Java Server Technologies
ORACLE Canada | 45 O'Connor St., Ottawa, Ontario | K1P 6L2
Green Oracle <http://www.oracle.com/commitment>
Oracle is committed to
developing practices and products that help protect the environment
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________ p2-dev mailing list p2-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/p2-dev
|