The reason is simple. The p2 planner is Java agnostic. It only knows about the capabilities and requirements that are provided to it. (Sidenote - this is what allows p2 to resolve any other kind of dependencies like RPM, deb, etc.).
For the planner to know about the packages coming from the EE, you need to provide an IU that describe this EE. Normally you should be able to find such an IU in the Eclipse release repo under the name "a.jre". Also if you use the mirroring application this IU should be brought in. HTH Pascal On 2013-02-01, at 6:08 AM, Tom Schindl wrote: > Hi, > > Yesterday in the night I tried to understand why IPlanner reports an > error when a bundle does a package import coming from the JRE which by > default is then exported through the system bundle. > > The reason I tried to understand this is that I've started build a > target platform which contains the complete set of plugins to develop > (including even org.eclipse.osgi, ....). You can see a description of it > at http://www.eclipse.org/forums/index.php/t/452288/. > > Is there a possibility to teach the resolver that e.g. javax.net.ssl is > coming from the JRE/system.bundle, I guess it would need to have EE > informations for this, right? > > Tom > > -- > B e s t S o l u t i o n . a t EDV Systemhaus GmbH > ------------------------------------------------------------------------ > tom schindl geschäftsführer/CEO > ------------------------------------------------------------------------ > eduard-bodem-gasse 5-7/1 A-6020 innsbruck fax ++43 512 935833 > http://www.BestSolution.at phone ++43 512 935834 > _______________________________________________ > equinox-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
