Community
Participate
Working Groups
Looks like dependency resolver uses current JVM when calculating list of system packages provided. This becomes a problem when compiling against JDK defined by BREE (see bug 362966) and when compiler using bootclasspath access rules (see bug 364076). I'll provide a fix and corresponding tests shortly.
Most of the work is done, including changes to target platform configuration and ProjectorResolutionStrategy. http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/diff/tycho-bundles/org.eclipse.tycho.p2.resolver.impl/src/main/java/org/eclipse/tycho/p2/target/TargetDefinitionResolver.java?id=ffd3905192b24032ffc74e71917b1534b0e1a1e9 Still need to do TargetDefinitionResolver.
How is this possible at all? I thought that p2 breaks this use case through the a.jre.javase IU hack (cf. bug 346174 and duplicates)
(In reply to comment #2) > How is this possible at all? I thought that p2 breaks this use case through the > a.jre.javase IU hack (cf. bug 346174 and duplicates) The new code filters out garbage a.jre IUs provided in p2 repositories, see ResolutionContextImpl.filterJREUIs. Then a proper JRE IU is generated based on the build target execution environment. The proper JRE IU is forced in to the resolved state as one of root IUs. Does this answer your question?
Pushed preliminary TargetDefinitionResolver changes to 364095_resolverBREE branch for now. Need to cleanup implementation before merging to master. http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/log/?h=364095_resolverBREE
Reworked .target resolver to honour project configured execution environment. This completes implementation of dependency resolution execution environment support. http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/commit/?id=857da0b4884bd1e024012f804546ffc47d2e69de