Guys,
 
AndroMDA now requires maven-1.0-rc2 in order to build successfully.  I've updated the AndroMDA from scratch page to reflect this.  I decided to go for the upgrade because of the fact that maven-rc1 doesn't support more levels of inheritance between POMs (project.xml), and that meant I had to duplicate information in sub module project.xml files.  For example, I had to have the currentVersion specified in 6 different project.xml files!  Now with rc2, all the shared information is now defined in the base level POM (i.e. the currentVersion). which is they way it should be.  Also maven-rc2 has much better memory handling and in that case AndroMDA builds much faster (from 5 minutes on my machine with rc1 to 3 minutes with rc2)
 
There is a minor bug in maven-1.0-rc2 that I mention: http://team.andromda.org/tiki/tiki-index.php?page=AndroMDA+From+Scratch  If you have a dependency on a maven plugin in your project and that plugin is downloaded during the build process then maven will not find the goal, once the plugin is in your local repository or $MAVEN_HOME/plugins directory then the goal will be found fine. 
 
In terms of AndroMDA, this means if you're building fresh the first time, maven won't find the andromda plugin and fail on the build, any run after, it will build fine. When you upgrade to maven-1.0-rc2 make sure you delete your maven plugins cache (%USERPROFILE%/.maven/plugins for windows, or $HOME/.maven/plugins for linux) before building.  After they release rc3 this will no longer be an issue (since this bug has been fixed in the current MAVEN-1_0-BRANCH).
 
Let me know if anyone has any questions/issues.
 
Thanks,
 
Chad
 

Reply via email to