Community
Participate
Working Groups
Since Juno M3 the EPP testing package contains a number of RAP JARs which cause multiple errors due to simultaneously present RCP JARs / bundles. org.eclipse.rap.jface_1.5.0.20111108-1014.jar org.eclipse.rap.jface.databinding_1.5.0.20111108-1014.jar org.eclipse.rap.rwt_1.5.0.20111108-1014.jar org.eclipse.rap.rwt.osgi_1.5.0.20111108-1014.jar org.eclipse.rap.ui_1.5.0.20111108-1014.jar org.eclipse.rap.ui.views_1.5.0.20111108-1014.jar org.eclipse.rap.ui.workbench_1.5.0.20111108-1014.jar We introduced a new bundle for Juno M3 - org.eclipse.jubula.ui.compatibility - which does have optional dependencies to RAP bundles. But these are not supposed to be present in our EPP testing package. As far as I could see there is no direct dependency to RAP neither in one of our features nor in the corresponding EPP testing feature; only the indirect dependency via the newly added "org.eclipse.jubula.ui.compatibility" bundle which itself is a dependency of our feature "org.eclipse.jubula.feature". Is there a way to add an explicit exclusion for the EPP package build for these optional bundles?
*** Bug 363813 has been marked as a duplicate of this bug. ***
In the meantime I read about bug 306279 and related / linked bugs - but I am still not sure how to add such an exclusion: Is there currently a known way to perform these exclusions / configure the non-greediness? Which steps have to be taken to do so? What I would like to achieve is: - exclude some of these optional bundle dependencies (to RAP) when - installing our Jubula feature into the IDE - building our Jubula feature into the EPP testing package - still fulfill / resolve these optional dependencies when installing / using some of our bundles in a RAP context
I added the recommended p2.inf to our bundle which has optional *rap dependencies: http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=f975fb0ddad3e8d90613d72fd241020bcc8ba1c6
This modification seems to have solved the problem. I verified manually that after installing the current Jubula feature (which includes the additional p2-information) into Juno M3 for Java developers there are no longer any optional RAP dependencies pulled into the IDE. As long as the upcoming Juno-M4 contribution of Jubula in the corresponding EPP testing package has not been verified this ticket should remain open and assigned.
I verified the Juno-M4 contribution of Jubula in the corresponding EPP testing package and optional RAP dependencies are also no longer pulled into the package.
Setting status according to comment 5.
