With maven 2 you only have to keep track of the jars that your code
depends upon. It is a royal PITA to try to use some component and then
have it die when you run it because of a ClassNotFoundException. So you
add the missing jar and get a different ClassNotFoundException.
Next, if you build several components each might use different versions
of jars. With Maven you can insure that your project is built and
packaged with only 1 version.
Maven has a whole bunch of reports in its website generation that we
find highly useful. Especially with regard to code coverage,
automatically running unit tests, and coding style adherance.
If you buy into maven's way of doing things then you only have to write
"build logic" for things that are unique to your project. With ant you
have to write everything.
Having said all that, I'm not sure why a Jetspeed customer really needs
to know about any build tool. I should be able to download a war or ear
file, install it into my container (perhaps with a configuration script)
and run it. I really should only be concerned about the build tool if I
want to modify Jetspeed source.
Ralph
Boyce, Keith Garry wrote:
I'm curious.. Many other successful open source projects exists without
maven? I know some do use maven but I can't establish the reasoning
behind it. AFAIK maven allows you to download jars associated with
project. Other than disk space and initial download time I don't see
what that buys you. It's just another piece that has to work which I
would prefer not to have to deal with. Why create an unnecessary barrier
to adoption? Am I missing something here about the benefits of maven and
what the advantages of using maven would be to this or any project for
that matter?
Garry
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
