------------------------------------------------------------------------------------------------------
Yes, I have pretty good idea what I need from JDT to properly support
multi-module/nested maven projects in m2e. I even did some exploratory
prototype couple of years ago to understand the problem and possible
solutions. Based on that prototype, what we need boils down to two
features.
We need to invoke java compiler from m2e builder directly, bypassing
JavaBuilder. I believe this is relatively small change to JDT,.
We also need to associate java sources+classpath+options with any
workspace folders, not just IProjects. This is a pretty big change, I
believe, and I was not able to implement it without breaking existing
API a little.
Last time I brought this up I was told "it's definitely out of scope for
the JDT team". This is why I decided not to invest any time into this
until we (Takari) can commit resources needed to do this ourselves, and
likely maintain JDT fork for some time.
[1]
https://bugs.eclipse.org/bugs/show_bug.cgi?id=356450#c15
------------------------------------------------------------------------------------------------------
4.) Best refactoring, quickfix and content assists support possibleIntelliJ has zero delay for content assists, which makes it feel much more responsive. Shortcut in IntelliJ are more consistent and simpler to use, for example to extract a String you do not have to mark the String first, the cursor position is sufficient. Eclipse leaves several great options unselected in its defaults, i.e., automatic placement of the semicolon.
Andy or Dani might be able to tell what is needed here.