Lessons learned from building Spring Tooling for Eclipse
We are building the Spring tooling for Eclipse for a long time now. Along that way, we made a lot of mistakes and learned a lot of lessons. This talk will discuss the most important lessons that we learned - and things we would do differently next time. Some of those lessons include:
why modifying the JDT compiler to support another language is a really bad idea - and what to do instead
why and how to load user code into the IDEs JVM - and why better not
why re-implementing language tooling in Java for Eclipse is a bad idea
how using Spring libraries as OSGi bundles can kill you - and how to survive
why using HTML inside of Eclipse can cause a lot of headaches (and how to avoid them)
The talk walks through those lessons (and more) and explains the details behind them in more detail. It is an ungracious reflection of our decisions, our ideas, and our implementations for the Spring tooling - and helps the audience to avoid making the same mistakes.
Martin Lippert