Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 341569

Summary: pde api tools fragments specify a specific version of the host bundle (1.0.201)
Product: [Eclipse Project] PDE Reporter: Kim Moir <kim.moir>
Component: BuildAssignee: pde-build-inbox <pde-build-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: major    
Priority: P3 CC: aniefer, curtis.windatt.public, daniel_megert, Olivier_Thomann
Version: 3.7   
Target Milestone: 3.7 M7   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Proposed fix
none
patch none

Description Kim Moir CLA 2011-03-31 23:31:42 EDT
This has caused the build to fail since the pde.api.tools (host) bundle version has changed to version 1.0.300.qualifier.
Comment 1 Olivier Thomann CLA 2011-04-01 08:43:12 EDT
I changed it for [1.0.201,2.0).
Comment 2 Olivier Thomann CLA 2011-04-01 08:49:03 EDT
Created attachment 192351 [details]
Proposed fix
Comment 3 Olivier Thomann CLA 2011-04-01 08:49:51 EDT
Released for 3.7M7.
Kim, could you please start a test build ?
Comment 5 Olivier Thomann CLA 2011-04-01 09:36:36 EDT
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.
Comment 6 Olivier Thomann CLA 2011-04-01 10:10:40 EDT
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.
Comment 7 Olivier Thomann CLA 2011-04-01 10:42:55 EDT
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.
Comment 8 Olivier Thomann CLA 2011-04-01 10:45:03 EDT
Released for 3.7M7.
Kim, could you please start a new test build or tell me how I can do it myself?
Thanks.
Comment 9 Kim Moir CLA 2011-04-01 17:22:43 EDT
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.
Comment 10 Olivier Thomann CLA 2011-09-09 17:19:14 EDT
Reopening. This was never fixed.
Comment 11 Olivier Thomann CLA 2011-09-09 17:30:56 EDT
Move to PDE/Build. It looks like the dependencies check is invalid. Setting as major as this prevents a build from being complete.
Comment 12 Curtis Windatt CLA 2012-02-15 12:38:43 EST
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.
Comment 13 Kim Moir CLA 2012-02-15 15:30:27 EST
Yes, see bug 362103
Comment 14 Kim Moir CLA 2012-02-15 15:30:45 EST

*** This bug has been marked as a duplicate of bug 362103 ***