No, I fully agree. JDT is our most heavily used language DT. I'm not sure messing with it is a great place to start.
in need of some love.
So, I wonder if we should be considering forming an Eclipse Project around all this. And silly enough, calling it the Eclipse IDE project so we can keep using this mailing list and the web site (which is Coming Soon, BTW). We could cover this cross-language
framework, an Eclipse IDE installer that Mike M was thinking of, and anything else IDE related that no one else is doing. Plus form a central gathering post for all the related projects (kinda like CDT is with PTP, TM, and LinuxTools). Or is this too much?
I added a comment to
, but thought that maybe I could get some more discussion here. Frankly, the idea of rewriting JDT or any mature *DT scares me. It is too late to do that and there will be lots of wasted time just to
get back to where we started from.
The idea of a common language infrastructure has value and is potentially doable. Perhaps providing some extension points and a bit of infrastructure that enables *DTs to interoperate and communicate would provide some nice incremental benefits. I'm thinking
in particular of features like search, navigation, content assist, and refactoring (particularly across JVM languages). This infrastructure would have to sit on top of JDT (or next to it) and would have to be opt in for each *DT. But, something like the
common navigator, which is fairly successful (despite some rough edges) shows that this kind of integration is possible.