karniv0re's Journal: Eclipse: The Loathe of My Life

Eclipse is bad, man. And I'm not saying that because I used it once and didn't like it. I have used it daily for 5 years. I remember it being pretty decent somewhere around the Helios/Indigo era. But once Juno hit, everything fell apart it seems. I'm currently still sitting on Juno, with two versions gone by now, because while, yes it is fucked up, it is a known level of fucked up. I don't know how much worse they've made it since then.

For a while, I kept a list of everything wrong with (my) Eclipse:

- SVN commit sometimes gets stuck.
        - Solution: Sometimes cancelling it and trying again works. Sometimes you have to restart Eclipse.
- Red Problem error on POM file after updating shared component
        - Solution: Manually update project under Maven
- JiBX binding fails when any change is made to the component
        - This is due to the JiBX autobuild plugin being fucked up and having to disable it
        - Solution: Do a clean install every time
- JRebel reloads forever, but doesn't execute
        - Solution: Stop server, recompile, start again
- Closing when SVN locks up locks the whole app.
        - Solution: Kill w/ task manager. Start again.
- Error shows in IDE, compiles w/ manual MVN command
        - Solution: Delete Maven Persisted Library from build path
- Debugging / Changes/ JRebel reloading causes IDE to lock up.
        - Solution: Kill w/ task manager. Start again.
- Toolbar gone for no good reason
        - Solution: Window -> Hide Toolbar (Why is it not "Show Toolbar"???)
- Shows errors after updating Maven dependencies in text editor.
        - Solution: Restart Eclipse
- "Perspective Switch Job has encountered a problem" when debugging from Java perspective and it hits a breakpoint and tries to flip you over to Debug.
        - Solution: Restart Eclipse
- Save stops working (ctrl+s, or :w in Vrapper)
        - Solution: Close editor (it will ask if you want to save, so say yes) then restart Eclipse
- Deleting project leaves closed project folder in package explorer
        - Solution: Restart Eclipse
- Link with Editor stops working in Package Explorer
        - Solution: Restart Eclipse
- WSDL file giving warning: WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: null ------------------------------------------------------------------------------ Nested exception is: java.lang.NullPointerException The WSDLAnalyzer was
  unable to validate the given WSDL File.
        - Solution: No idea. This is apparently a bug in WST or something.
- Parent project of a multi-module project shows as in error with "Import cannot be resolved"
        - Properties -> Project Facets -> Check Dynamic Web Module, Java, Javascript
- XSD shows as an error in project with "src-resolve: Cannot resolve the name 'xxx:whateverType' to a(n) 'type definition' component."
        - Solution: No idea.

Notice how most of the solutions end with "Restart Eclipse." Ugh. It's the new Windows.

Unfortunately, I can't use IntelliJ. As much as I love some of the things you can do with IntelliJ, I gotta have multi-module support. I don't work in a single module. I work in several at the same time. IntelliJ's limit on that is a deal breaker.

Anyway, I've been trying to clean up my workspace all day, which is proving to be a Sisyphian task. Screw this. I need to code. I'll just have to live with the false-alarm red-Xs and warnings. Just like I live with Eclipse. *fart noise*