The following upgrade steps are needed if you want to upgrade your project from Mod4j 1.0.1 to Mod4j 1.1.0 .
With this release of Mod4j we've moved to Eclipse Galileo. The new Mod4j Eclipse plug-in will not work under Eclipse Ganymede, so if you did not upgrade already, now is a good moment to take this step. It is not so hard, just follow the Mod4j 1.1 Getting Started for this release.
The generation of Spring configuration files has changed. A file named
applicationContext.xml
is now generated in
generated-resources
followed by the package root directory for each module. In the previous
versions a file with the same name
was generated just once under
src/main/resources
. This last file will
conflict on the classpath with the generated one. The file
applicationContext.xml
under
src/main/resources
will have to be removed.
With this release Mod4j has improved the Maven configuration for your application. Follow the next steps to adjust the Maven configuration in the right way.
All changes apply to the parent-pom of your application. The parent-pom (pom.xml) is located at the root of your project (if you didn't change its location).
Some of the DSL model syntax has been improved.