Community
Participate
Working Groups
Build Identifier: I20100608-0911 Two versions of a bundle exist in the target platform. One feature includes version 1.0.0, another feature includes 2.0.0. When site.p2 is invoked, the resulting repo only contains version 2.0.0 of the bundle, when it should contain both. Invoking an export feature correctly results in a repo that contains both versions of the bundle. Reproducible: Always Steps to Reproduce: 1. Two versions of a bundle in the target platform 2. Two features that include each of the bundles by explicit version. Example: <plugin id="com.example.bundle" download-size="0" install-size="0" version="1.0.0" unpack="false"/> 3. Run site.p2 on a top level feature 4. Examine repo
Buckminster should allow two versions of the same bundle if the version difference is more significant then just the qualifier. Buckminster will not allow 1.0.0.abc and 1.0.0.xyz but it should allow 1.0.0.abc and 1.1.0.abc. Can you please attach an example that provokes the problem?
Created attachment 174634 [details] Test Projects archive Archive file with test projects and features.
Created attachment 174635 [details] Target Platform Target Platform files
I attached a project archive and target platform files. I'm sorry if it is confusing, but there are three bundles: "one, two, and three". The target contains two different versions of bundle one. Bundles two and three require one but have different (non overlapping) version range constraints. I created two different features to package bundle two and three. Each include their respective bundle, and also the needed version of one. Finally there is a top level feature on which to invoke site.p2 that includes the other features. The repo resulting from invoking site.p2 will only contain a single version of bundle one. The repo resulting from invoking a feature export through the PDE tooling will contain both versions of bundle one (which is the desired behavior).
The cspec dependencies had a bogus version range. This is now corrected. The fix was committed to helios-maintenance, rev 11507. Thanks Jason, for an excellent test case.
*** Bug 320345 has been marked as a duplicate of this bug. ***
I added a JUnit test case based on the attached sample to the Buckminster PDE test suite.
i updated this morning to the new buckminster version: Buckminster - Core 1.3.1.r11513 I still get the same problem. Was the fix included in that release?
The fix is in the o.e.b.pde, revisions 11507 or higher. Did you start with a fresh workspace?
using: Buckminster - PDE support 1.2.1.r11512 same problem in new workspace. Same errors as described in bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=320345 Do you need anything more from me?
