Lately, I noticed my libraries weren’t published to Tomcat when I used a Maven project in Eclipse, even though it was standard war packaging. Since I mostly use Vaadin, I didn’t care much, I published the single vaadin-x.y.z.jar to the deployed WEB-INF/lib manually and I was done with it. Then, I realized it happened on two different instances of Eclipse and for the writing of Develop Vaadin apps with Scala, I used 3 different libraries, so I wanted to correct the problem.
Since Indigo, the Maven Ecliple plugin formerly known as m2eclipse became part of Eclipse release . The name of the plugin also changed from m2eclipse to m2e. This was not the sole change, however: the number of tabs on the POM has shrinked drastically, and the features as well. This will probably be the subject of a later post since I feel quite cheated by the upgrade.
In this article, I will show you how to tweak Eclipse so that you will be able to code 'classical' webapps in Scala. Eclipse has a plugin that let you help develop with Scala. The plugin is by no mean perfect , but it gets the job done, letting you create Scala projects that automatically compile Scala code with scalac.
Using an IDE to develop today is necessary but any IDE worth his salt can be enhanced with additional features. NetBeans, IntelliJ IDEA and Eclipse have this kind of mechanism. In this article, I will mention the plugins I couldn’t develop without in Eclipse and for each one advocate for it. m2eclipse Maven is my build tool of choice since about 2 years. It adds some very nice features comparing to Ant, mainly the dependencies management, inheritance and variable filtering. Configuring