On Tuesday 06 January 2004 19:38, Lofi Dewanto wrote: [ ... snip ... ] > As you only have *one* build file for each cartridge, I don't > see any reason to make the build file more complicated than > this ;-) > > It would be cool to separate AndroMDA in sub-components like: > - the AndroMDA core (pure MDA tool). > - the AndroMDA cartridges (architecture like J2EE, .NET, etc.). > - the AndroMDA examples (how to use AndroMDA core + cartridges > + applications)
Well, I don't really know Maven (never used it yet, only read about it and heard from people who use it), but if I'm not mistaken, then Maven is all about managing just that kind of setup. Including cool stuff like - automated daily builds, including publication of the "latest and greatest" version on the project web site. - automated QA runs on the current build (JUnit, FindBugs, whatever), of course with automatic publication of the test results - handling dependencies on subcomponents. Example: You're only interested in developing the "Foo" cartridge, so you set up a CVS repository for it and configure Maven to use the current build from the main AndroMDA web site for all dependecies. In short, this sounds like just the situation where we can actually profit from Maven. The only downside I can see is that more people are familiar with Ant than with Maven, which makes it a bit more difficult to attract new developers. But that's what we have a Wiki for, isn't it? :-) My 2â-cent, Richard -- Richard Kunze [ t]ivano Software, Bahnhofstr. 18, 63263 Neu-Isenburg Tel.: +49 6102 80 99 07 - 0, Fax.: +49 6102 80 99 07 - 1 http://www.tivano.de
pgp00000.pgp
Description: signature
