| Summary: | [legacy] IBundleGroup.getBundles() returns no installed bundles, throwing an IOException on parse | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Joel Cayne <jcayne> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | kathy, pascal, paulslau, woskimi |
| Version: | 3.5.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 242621 | ||
|
Description
Joel Cayne
This is a critical issue for TPTP 4.7.0 (and our consuming products). Ah, I understand the problem. You are installing using the p2 bundle pooling concept which combines the bundles/features from multiple installations together in the same directory. This layout of bundles and features is completely unknown to legacy update manager so it will never be able to find the features. Even if it did find the features, it would return the wrong answer because it doesn't know which features belong to the profile that is running. I think the best solution for this is to address bug 236709 - have p2 provide the bundle groups since it understands the layout of p2 metadata. You will notice on the Equinox download page that the p2 installer is listed as "early access". This is because the installer is not under active development, and the bundle pooling approach used by the installer is completely untested. What is TPTP using the installer for? TPTP does not use the installer but this setup was reported in bug 242621. This scenario seemed to closely match the case discovered in bug 306703 which was requested by a consuming product. (In reply to comment #2) > I think the best solution for this is to address bug 236709 - have p2 > provide the bundle groups since it understands the layout of p2 metadata. > John, would you be able to suggest how we can access these bundle groups using p2? Thanks. (In reply to comment #1) > This is a critical issue for TPTP 4.7.0 (and our consuming products). Note, this is no longer a critical issue for TPTP 4.7.0 (and our consuming products) since the root cause of our symptom was Equinox defect https://bugs.eclipse.org/bugs/show_bug.cgi?id=316650. *** This bug has been marked as a duplicate of bug 316650 *** *** Bug 325723 has been marked as a duplicate of this bug. *** Re-opening since the same behavior still exists as seen through bug 325723 comment 12. *** Bug 325723 has been marked as a duplicate of this bug. *** |