Let's be clear here Up till now I have been talking about a maven plugin for AndroMDA use, not for building AndroMDA
i.e. if I am using AndroMDA in my project & my project is already using maven, then I would use the maven AndroMDA plugin to build the AndroMDA portions of my project So in this way, there is no impact on current users of AndroMDA (they continue to use their own Ant scripts) or current builders of AndroMDA since nobody is being forced to use maven. It would also be possible to move the AndroMDA project itself over to a maven based build, but that is a completely different topic, unrelated to having a maven plugin for AndroMDA. IMO there are many reasons to use maven in your project, not the least of which is very high levels of reuse, excellent dependency management and a very active community (obviously Ant has an even more active community). Maven however is a controversial choice to some and so it should be left up to individuals and organizations to decide (as far as AndroMDA use, not AndroMDA building) I hope that help clarify the discussion Matthew ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
