| Summary: | IDE won't start after "install everything" in Indigo M5 | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | David Williams <david_williams> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | pascal, thomas |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 336469 | ||
| Attachments: | |||
|
Description
David Williams
Created attachment 188393 [details]
configuration log file after startup failure
Created attachment 188394 [details]
dot log file created during "install everything" attempt
In the course of my testing, I next tried to "install everything" by installing one category at a time (except nothing/never from EclipserRt cateory). The IDE was restarting ok, until the last category: SOA Tools. Via some notes I've seen, some (or all?) of these "stp features" should not be part of Indigo (but .. I am still trying to track that down). This time, after installing this last SOA category, the IDE did not start. First time, did not even pop up a dialog, but was a "hung"? process, or something. So, killed that, and tried to restart. Then got the dialog, and this time did say "see .../configuration/xxx.log". Oddly, there was not much in that! I'll attach both config log and the .metadata/.log which has messages from the many previous "install category" steps. Hopefully someone can spot something in logs that focus attention on worst problem? Or else I guess we'll have to wait till someone else reproduces in more meaningful way? (Again, I was doing this work on Linux ... some of the message in the log sound like something needs some windows filters?) Created attachment 188400 [details]
configuration log after latest startup failure
Created attachment 188401 [details]
log file from "install category by category" runs
I suggest you move this bugzilla to rt/equinox/p2. The root NullPointerException appoints p2 as the culprit. Sure ... is your mouse broken? :) [i.e. I think a committer in p2 could move it there themselves if that's where they thought it belonged]. (In reply to comment #7) > Sure ... is your mouse broken? :) [i.e. I think a committer in p2 could move it > there themselves if that's where they thought it belonged]. I did consider doing that :). But since the problem manifests when installing everything in the train, and since that probably only happens in the context of the train, I felt that you'd be the judge of if a move would be the right thing to do. Perhaps you'd feel it more comfortable keeping this bugzilla as a "train issue" in cross-project and create a new one referencing the NPE in p2 and then add a dependency. On the Mac, I just installed all of the SOA tooling category and restarted fine, and then I tried Object Team without any problem. *** This bug has been marked as a duplicate of bug 349105 *** |