Comments on: Maven Adoption Curve

By: Andrew Williams

Andrew Williams — Tue, 01 Sep 2009 15:26:16 +0000

Bjorn:
Or get into the HeadsUp! betas (http://headsupdevelopment.com) which will take care of everything plus repository management in one app…

Folk should realise that the “a skilled developer” who realises they do not need transient dep from a project dep can mark it as excluded – much easier to debug should the project requirements change. Always have a trail to follow – a dir of jars is no help to anyone next time you want to update a single dep in a tree of dependencies…

By: Björn

Björn — Mon, 18 May 2009 19:20:35 +0000

haha, typical Java world to recommend a repository manager as a remedy. Yay, another layer on top of the zillion other layers. Yet another tool to learn. Fun times…

By: Luke Nezda

Luke Nezda — Fri, 13 Feb 2009 18:53:21 +0000

Bill -

1. The only time I saw a corrupted repository, it was because I ran out of disk space. Bad hard drive ? Windows maybe ?

2. jar bloat: Usually using others’ code is better than re-writing it, but if you depend on jars you don’t need, that’s just laziness I guess and offly easy to remedy.

3. This is what checksums should put your mind at ease using external repositories

4. Not sure what to say here – it’s generally felt straight forward and well documented for me across many projects and environments.

By: Shaaf

Shaaf — Thu, 12 Feb 2009 15:41:17 +0000

All but in “fun off course…”. I would agree with Bill.

By: Bill Kratzer

Bill Kratzer — Wed, 11 Feb 2009 12:59:59 +0000

My issues with Maven are quite simple:

1. Maven repository corruption seems to be frequent enough that I just simply do not trust it. I’ve seen this on many projects, on many workstation types, and many clients. It simply should not happen.

2. I’ve seen many projects suffer from unnecessary “jar bloat” when using Maven. A skilled developer can always manage this problem much better — and it really isn’t the big time drain that the Maven-ites make it out to be.

3. Having to rely on an external repository for downloading jars seems like an insane idea to me. I want my project and its dependencies to be under version control so that I can be 100% sure that I am building the same binary artifact each time.

4. On many client projects, I have seen more people spending a lot of time with “troubleshooting Maven”. Instead, they should be writing code to solve real business problems.

I suspect in five years we’ll be looking back at Maven the same way we all fondly look back at EJB 2.0. :-)