1. 2


    “Test source folders will be preselected in the New JUnit Test Case-Wizard”

    YAAY!!! This has been a (minor) annoyance for a long time. Eclipse defaulted to putting my tests in src/main/java instead of src/test/java for maven projects, and fixing it required me to tab back through a good dozen controls or switch to the mouse. Every time I made a new test case.

    This is going to save me many, many seconds.

    1. 10

      This feels spot on. Whenever I get inspired to try to fix something I don’t like about Eclipse, I spend a few hours hacking and then get so discouraged fighting the complexity that I give up. The only good documentation is for the deprecated 3.x API. The 4.x API is much more complex and I can’t see any advantage to it.

      It’s really a shame, because Eclipse seems like a better Java editor than IntelliJ to me, which is why I still use it. Writing Java in Eclipse feels totally different than any other language/editor experience - I’m manipulating Java syntactic elements rather than editing text. The shift-alt-arrow “select java syntactic element” operation is the best example. Instead of selecting by text-editor concepts like “word” or “line”, it’s selecting by Java concepts, like block or method call. I couldn’t find the equivalent operation in IntelliJ

      There’s a quote by someone like Martin Fowler where he says that he’d like an editor that works exclusively by ADT transforms (I couldn’t find the exact quote). At it’s best, Eclipse feels like that. I assume that’s what Lisp people feel like when using paredit.

      But wow, is the rest of the experience janky as hell. I’ve maintained RCP apps before, I’ve been writing Java since the 90s, and it’s open source, so in theory I should be able to fix the problems I see. If it weren’t so complex underneath, I’m sure it would still be winning.