Actually, I am pretty much against maven right now. I don't have that
much experience with it, but my feeling is that it introduces complexity
with no real benefit. I prefer to know that by checking out the
repository (via cvs, svn, whatever) I've got *all* the tools I need to
build the application.
I took over a project a couple months ago that used maven and the whole
thing was totally f**ked up. I never even got it to build properly
before giving up and rewriting the whole build process from scratch
using just ant. Maybe the original author didn't set it up right, but
that definitely turned me off to maven.
-- Allen
Matt Raible wrote:
I don't see a problem with it - but if it ain't broke - why fix it? ;-)
Matt
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.
The difference between Ant and Maven is like that between a
procedural and a declarative language. Instead of telling Ant what
to do in order to build, you tell Maven what you want done and it
figures out what needs to be done based on the XML configuration
file. Maven automatically tracks and downloads dependencies for you,
versions the artifact, produces documentation website with JavaDocs
and unit-test coverage reports.
I've "mavenized" Roller 1.x branch and would be happy to contribute
that to the project. Let me know if there is any interest in that.
You can learn more about Maven at http://maven.apache.org
Max
