Bug 236378
| Summary: | Eclipse 3.1.2 Binary Hangs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Mike Millson <mmillson> | ||||
| Component: | eclipse | Assignee: | Ben Konrath <ben> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | eclipse-bugs | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5.0 | CC: | marshall.culpepper, max.andersen | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2007-04-16 08:30:40 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Mike Millson
2007-04-13 14:55:20 UTC
Created attachment 152546 [details]
Startup error message.
I don't think this should be filed against the Eclipse package. Perhaps there's a JBossIDE bug repository somewhere? I agree it's not an eclipse package issue. I wasn't sure what component to file this against. It's not just a JBoss IDE issue. It also happens with the stock Eclipse 3.1.2. Any suggestions as to what component this belongs to? Really it's an issue due to the use of xpcom by Eclipse 3.1.x and the fact that RHEL5 isn't supported by them. This is probably as good a place as any to track it. But really it will probably require some fixing within JBossIDE itself (ie. patching SWT). Ben can probably show how we fix it with 3.1.x in Fedora. could we change the title to represent the real issue ? its general for Eclipse not just jbosside Can you try stock 3.2.2? Stock 3.2.2 starts up fine. It doesn't have this issue. (In reply to comment #7) > Stock 3.2.2 starts up fine. It doesn't have this issue. Phew, I thought we got it all fixed upstream for 3.2.2 :) I'm tempted to close this but but perhaps only when someone files something against the offending product (JBossIDE, RHDS, whatever) to upgrade their SDK to 3.2.2. Please close this when that's done. Thanks. I previously filed the following bug on the JBoss Jira: http://jira.jboss.com/jira/browse/JBIDE-469 Just curious, what is the explanation for why I can start up using java -jar startup.jar, yet executing the eclipse binary directly fails? And why after doing that can I exectute the eclipse binary and it works? probably some difference between the two ways of starting and that the working one manages to write enough metadata so the other one doesn't hit is bug - what i don't know. I'm going to close this bug because the 'eclipse' component under the RHEL 5 product should be used for bugs that are in "Red Hat Eclipse", the version of Eclipse that is integrated into RHEL 5 itself, and not for any 'layered' version of Eclipse. This is not say the Fedora / Red Hat Eclipse team can't help with issues like this, it's just the wrong place to have the discussion :-) If a similar problem happens in the future I think the best thing to do would be to file a JBoss IDE bug and send a message to eclipse-list if you want us to investigate. Please read the bug - this has *nothing* to do with JBoss IDE. It's a plain vanilla eclipse + RHEL issue. Where should issues like this be discussed if not in RHEL bug db (+ Eclipse bug db if an general eclipse issue is found) ? (In reply to comment #12) > Please read the bug - this has *nothing* to do with JBoss IDE. I did read the bug. JBoss IDE includes a plain vanilla Eclipse therefore the problem is with JBoss IDE. And yes, I understand that it's really just the upstream Eclipse SDK that's causing the problem but it's unrealistic to expect a random Linux binary to work perfectly with RHEL-5 - especially one that doesn't even claim to support RHEL-5. Red Hat Eclipse includes a number of changes to the SDK to ensure that it works with Fedora and RHEL. > It's a plain vanilla eclipse + RHEL issue. Right. But like I said, the eclipse component is for "Red Hat Eclipse", the version of Eclipse that is integrated into RHEL 5, not the upstream SDK that doesn't support RHEL-5. > Where should issues like this be discussed if not in RHEL bug db > (+ Eclipse bug db if an general eclipse issue is found) ? If you want to include a plain vanilla Eclipse SDK in a product then you should request RHEL-5 support for the 3.1.2 SDK in the eclipse.org bugzilla. Since they probably won't fix such a bug, the only solution would be to include a patched version of the SDK in your product if you want it to work with RHEL-5. Issues surrounding this work should be discussed in JBIDE-469. ok - so we should put this in RHDS; not JBossIDE. I've created http://jira.jboss.com/jira/browse/RHDS-44 Note: this seems to only be relevant for 3.1.2, which we won't be using anymore; but please fill us in with any details you have on special things that previously have been needed to run Eclipse on RHEL on that issue. This is critical to know for RHDS. Thanks. |