Bugzilla – Full Text Bug Listing
| Summary: | Could not start: org.eclipse.equinox.common (...). It's state is uninstalled. | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Dani Megert <daniel_megert> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | akurtakov, markus.kell.r, pascal, tjwatson |
| Version: | 3.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
|
Description
Dani Megert
That looks to be coming from p2. Perhaps p2 uninstalled something it did not think it should? Okay, I found the problem: due to bug 305847 'org.eclipse.equinox.common' was two times in my dev workspace as binary plug-in. Steps to reproduce 1. start with new workspace 2. import 'org.eclipse.equinox.common' as binary plug-in 3. import 'org.eclipse.equinox.common' as binary plug-in again without deleting the first one ==> workspace contains: /org.eclipse.equinox.common /org.eclipse.equinox.common_3.6.0.v20100315 4. launch Eclipse ==> Could not start: org.eclipse.equinox.common(reference:file:/C:/eclipse/workspaces/tmp2/org.eclipse.equinox.common/:64). It's state is uninstalled. Given Dani's steps this is not a p2 problem. Given that it does not look like there is much to do there and that it does not seem to me like there is a problem in the fwk either, I'm closing as dupe of 305847. *** This bug has been marked as a duplicate of bug 305847 *** "It's state is uninstalled." needs some grammar love. Furthermore, the error message is quite confusing. After all, the bundle is there, it's just duplicated. I would expect a message that not only tells me that the second instance of the bundle could not be installed, but also why. In other cases (e.g. if there's a newer version available or if the BREE is not met), I also get more clear messages. Moving to Equinox Framework, please pass on if that's not the right component. I agree with reopening for two reasons: 1. The bundle with that version is installed and started, so the message is at least very misleading. 2. the '-debug' option fails to report a warning about the duplicate singleton bundle, which it normally issues when two versions of the same bundle are present. ==> that message seems not be logged when the versions are the same When I manually change the bundle's version the warning is issued again (good) but this causes errors to be logged (see bug 306684). The generated bundles.info seems invalid: org.eclipse.equinox.common,3.6.0.v20100315,file:/Users/watson/Documents/workspaces/test/bug306684/org.eclipse.equinox.common/,2,true org.eclipse.equinox.common,3.6.0.v20100315,file:/Users/watson/Documents/workspaces/test/bug306684/org.eclipse.equinox.common_3.6.0.v20100315/,2,true It has two entries for the same version of equinox.common. This seems to be a flavor of bug 306684. The message you referring to in comment 5 is actually a System.err println from org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier, not the framework. Moving back to p2. I will also put a comment in bug 306684 about the case when you have multiple plugin projects with identical BSN and versions. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug looks ancient is it still reproducible ? A dialog is now shown, with an error message saying that two versions of that singleton bundle exist. If I choose to continue, I can reproduce this bug, but I think what we have is good enough. |