> <quote> > 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. > </quote> > Yes, I don't care if AndroMDA uses Maven for building AndroMDA itself. > What I care is for building the application (<andromda> Ant task). > I really hope that the Ant task will stay there... If we have > the choice like you said, then this is ok.
It is worth noting that the AndroMDA maven plugin *USES* the AndroMDA Ant task. So there is no chance that the AndroMDA Ant task will go away. Anyone would have the option of calling the Ant task from Ant or from maven. There is perhaps some small misunderstanding about how different maven is from Ant. Maven for the most part very heavily relies on Ant tasks from many different places. This is certainly the case for the AndroMDA maven plugin. It is build on top of the AndroMDA Ant support. 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
