I don't object to making it easier to build Roller with Maven, but I'm
-1 on switching to Maven or requiring that Roller devs maintain or
support Maven scripts. Like Allen, I've had bad experiences with Maven.
- Dave
On Sep 16, 2005, at 8:43 AM, Henri Yandell wrote:
On 9/13/05, Rudman Max <[EMAIL PROTECTED]> wrote:
How do people feel about "Mavenizing" Roller? For those who are not
familiar with it, Maven is "a software project management and
comprehension tool". It's is somewhat similar to Ant, in fact it uses
Ant goals under the hood (though upcoming Maven2 does not), but it
also keeps metadata about the project which allows it to be much more
intelligent.
All this means is adding a project.xml (and probably
project.properties and maven.xml as well) to the top level. Sometimes
can be quite tricky as Maven encourages a simpler build system than
most Ant scripts often end up being, so the Mavenite has to go around
the houses to get it all to work.
If you can write the maven files without needing to change the build
system (ie Ant people won't notice) then the only negative would be
the need to maintain the maven files.
To Matt's "why fix it?". Maven brings build standardisation and
encourages simplification. Having been well and truly brainwashed by 4
years of Maven use, I just 'love' discovering a new project and having
to unravel their custom Ant scripts :)
So I'm +1 to Max supplying the files if he feels the itch, and
provided it doesn't interfere with the Ant system, checking them in.
Otherwise the Ant stuff works fine.
Hen
