Comments on: Maven would be cool if…

By: Daoud AbdelMonem Faleh

Daoud AbdelMonem Faleh — Wed, 19 Mar 2008 00:09:54 +0000

building hibernate or OSS management this was a my post about maven few months ago trying to build hibernate from source tree..
just painful..

Regards.

By: soloturn

soloturn — Wed, 05 Mar 2008 18:04:30 +0000

would it be worth using http://incubator.apache.org/buildr/ ?

By: Derek Adams

Derek Adams — Wed, 27 Feb 2008 17:11:48 +0000

I know what you mean. We have a bunch of projects that are deployed as sars, wars, and ejb3 jars. I spent a week trying to get the standard plugins to do what I wanted and was never satisfied with the results. I ended up adding assemblies for everything and, even though it works, the whole build kinda seems like a hack now.

By: Avishay

Avishay — Tue, 26 Feb 2008 20:09:11 +0000

We have just finished writing a full build environment for a very big project containing over 300 maven modules. Reading this blog reminded me all the things we had to put up with while using maven.
Yes, of course , it is better than what we had before!(ant), but dealing with all the problems such as:
The plugins, the transitive dependencies issues, the awful XDoclet, maven-ear/war-plugin not working, the lack of Documentation …
I’ve come to realize that I realy need the control of all that is going on inside the build, which ment writing most of the plugins by myself.

My recommendations:
A realy good place to start is an opensource project called jfrog (www.jfrog.org) which contains several maven2 projects.
If you want to write your own plugin, look at Maven Anno Mojo project which allows you to use Java5 @Annotations instead of XDoclets.
JadePlugins - contains various maven plugins for assembly,multijar and so on ..
Dependency Analyzer - nice graphical tool gives you an overview of your dependencies

By: Tobias

Tobias — Mon, 25 Feb 2008 20:20:37 +0000

We had major problems with Maven 2 in a bigger “sort of” SOA project. The packaging stuff was a mess, the dependency stuff was not really helpful since we ended up managing all transitive dependencies by hand and we had to ditch the repository approach for proper release management based on a baseline approach.

All in all it just enforced a uniform directory and sub-project structure for all the service projects. And we ha to dedicate one person to manage all the pom.xml files and dependencies and such.

By: Marcus

Marcus — Sat, 23 Feb 2008 21:45:41 +0000

Well, of course, it blows. One size really doesn’t fit all, and if it did, what a boring place to be!

By: Ryan J. McDonough

Ryan J. McDonough — Sat, 23 Feb 2008 20:29:35 +0000

For the most part, Maven is great and saves a lot of bullshit. But when it comes to tools like the EAR plugin, its just freakin’ blows. The documentation is crap and doesn’t cover enough cases. As with most Maven plugins, the documentation is half-assed.

Packaging can be a complex process depending on what industry you’re in and how the application is going to be deployed. The current EAR plugin seems to suit the needs of the folks who wrote it at the time. Exclusions are a pain in the ass and non-intuitive. Things get worse with the WAR plugin. Anyone up for writing a better one? This thing is killing me on my current project.

By: alrubinger

alrubinger — Sat, 23 Feb 2008 06:38:10 +0000

A few observations I’ve made over the past few months:

The Bad:

* Agreed, often the standard plugins are non-intuitive and difficult to configure. I often find myself looking through the source to see what the plugin is expecting.
* Dependency Management is stupid simple at first glance, but once you take into account transitive dependency resolution, things get complex quickly due to the “nearest version wins” model. Frequent use of “mvn dependency:tree -Dincludes=org.me.whatever” helps.
* Defining metadata on the plugins is done in an XDoclet-esque fashion, embedding annotations in Javadoc. So you lose this information at runtime (if you’d like to subclass an artifact to make a plugin, for example).
* Local repositories easily fall out-of-sync; if a snapshot is removed from a networked repo, this change is not reflected locally.

The Good:

* The community at #maven on Freenode IRC is very helpful.
* The Plugin architecture is well-designed, making custom Mojo development easy and powerful.
* I’d rather spend my time developing custom plugins for Maven in Java than wrestling with Ant scripts.
* Antrun Plugin allows for stepwise Maven migration

S,
ALR

By: billburke

billburke — Fri, 22 Feb 2008 20:07:38 +0000

What I *reallY* like about maven is that I can just point Intellij to a pom.xml and everything just works.

By: Dave H

Dave H — Fri, 22 Feb 2008 19:46:30 +0000

The only thing I like about maven is the dependency management. I keep meaning to give Ivy a try, but never seem to get around to it.