Ok ...well, then let me also sum up my pain points with maven2 over here.
o It updates itself and you might end up having different behaviours across different installation. This should be fixable by an appropriate release handling. SNAPSHOT dependencies should not be allowed for a release plugin. The default should be: only update maven plugins on explicit request. o The stdout is just horrible and quite often disguises the actual root cause of failures in noise. The log level is more annoying than useful. There is a difference between a stdout and a log file. (What is it with all these "------------------"?) o It's just not clear what goals/plugins are available. Forcing something like "svn help diff" style help for all plugins would be nice, too. o Reporting for multimodule projects is just horrible inconsistent and doesn't even work with many plugins. IMO every report plugin should be *required* to implement an appropriate interface to support report aggregation. o Too much magic in the reporting section. If you leave out all the reports you get the default reports. You have to explicitly turn them off. Not straight forward. Especially annoying in a multimodule setup. o Downloads are not getting verified. I had it a couple of times that a mirror was broken and instead of poms or jars I ended up with html ...which screwed up my local repo. Cleaning up the repo was tedious ...so I ended up deleting my whole .m2/repository folder and re-download all! o Single artifact per pom. This concept pushes projects that only want modules based plugability into a multiproject setup, sometimes creating unnatural separations. A common test module to work around shared testcode is one example, this and attached artifacts further blur the concept. A general over-modularization is what happens. (how many maven artifacts are there?) o Make surefire settings 'printSummary' -> false and 'reportFormat' -> plain the default o Absolutely don't understand why a parent pom cannot generate an artifact o The eclipse plugin is a first step ...but needs further fixes and work. o Would be great to do the downloads of all transitive deps before *any* builds are starting. A bit more the "apt-get" style "I will download these artifacts". Half way through the build trying and failing to download an required artifact is annoying. In general maven2 is a great idea but feels much more complex than maven1 ...which is not exactly a good selling point. The implementation itself is ok as long as you deal with small and easy projects. Then it helps to save time. As soon as the projects become bigger and more complex it becomes a pain to work with. Go an try to build cocoon trunk for example. In the end I am much less enthusiastic. I cannot say it helped me to save much time anymore. (Spent way too many hours on the multiproject stuff) But I like the ideas and as I don't really want to go back to "ant" there is not much else I can do but sticking with maven. Just hope things will get better ...soon. cheers -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
