Comments on: Upgrading to Maven 2.1.0 on Macintosh OS X

By: Robert

Robert — Mon, 23 Mar 2009 13:22:26 +0000

@Brett – some minor ones, like the POM format got tightened, but the really annoying one for us was a change to the maven-dependencies-plugin (or more likely to one of the plexus module it uses) that broke the packaging of one of our EAR modules. The annoying part is that when we went back to 2.0.9, we still had the issue – we had to blow away the local repository to get rid of the plugins.

It’s probably something wrong in our packaging that will be easy to correct once we identify it, but we’re fairly gun-shy when it comes to Maven upgrades – there have been more than one upgrade in the past where we couldn’t get a set of poms to work with both Maven 2.0.n and 2.0.(n+1). We haven’t yet got around to isolating the problem – too many other things on.

(FWIW, most of our problems have been with the dependencies and the assembly plugins)

By: Brett Porter

Brett Porter — Mon, 23 Mar 2009 08:14:56 +0000

@Robert – which issue is causing you problems in 2.0.10?

By: Scot Mcphee

Scot Mcphee — Mon, 23 Mar 2009 04:08:49 +0000

Ahh right. I’m just starting a new project, so for the moment, past compatibility doesn’t concern me, but it might later when I want to build some old projects.

By: Robert

Robert — Mon, 23 Mar 2009 03:47:49 +0000

I did basically the same thing, but I left /usr/share alone, and put my new Maven install in /opt…

haven’t been game to try 2.1.0 yet; 2.0.10 broke-the-world again for me.