Community
Participate
Working Groups
This has caused the build to fail since the pde.api.tools (host) bundle version has changed to version 1.0.300.qualifier.
I changed it for [1.0.201,2.0).
Created attachment 192351 [details] Proposed fix
Released for 3.7M7. Kim, could you please start a test build ?
Test build here https://hudson.eclipse.org/hudson/view/Eclipse%20and%20Equinox/job/eclipse-equinox-test-N/336/
Reopened. Test build failed. /opt/users/hudsonbuild/workspace/eclipse-equinox-test-N/builds/N201104010911/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.build_3.6.100.v20110310/scripts/genericTargets.xml:111: Processing inclusion from feature org.eclipse.pde.api.tools.ee.fragments: Bundle org.eclipse.pde.api.tools.ee.cdcfoundation10_1.0.0.N20110401-0911 failed to resolve.: Host plug-in org.eclipse.pde.api.tools_[1.0.201,2.0.0) has not been found. This makes no sense. I provide a version range for the host of the fragment. It looks like the range is seen as a plugin version. I'll investigate.
I think the easiest way to fix this is simply to get rid of the version range. There is no real need to a version there. We used to have it to prevent for fragment from being installed on a version of API tools that could not support detection of invalid reference inside System libraries. I'll remove it and I'll release the change.
To make sure removing the version range doesn't cause potential failures because the format evolved over time, I'll simply use the new host version to replace the old one. Like that we can be sure that the current version of the host work with the appropriate version of the fragments. This is the safest approach at that time.
Released for 3.7M7. Kim, could you please start a new test build or tell me how I can do it myself? Thanks.
Created attachment 192391 [details] patch Olivier, the build is still failing and I don't know why. To avoid this problem temporarily I've disabled the building of the pde.api.tools.ee.fragments feature in the build so tonight's build can proceed.
Reopening. This was never fixed.
Move to PDE/Build. It looks like the dependencies check is invalid. Setting as major as this prevents a build from being complete.
The fragments specify a minimum host version currently. It sounds like this was a releng/build problem that was treating the ranges as specific versions. Kim, has this been corrected in 3.7? We are getting the fragments built in 3.8 builds now.
Yes, see bug 362103
*** This bug has been marked as a duplicate of bug 362103 ***