commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Carman" <>
Subject RE: [all] Maven 1.0 vs. 2.0
Date Fri, 14 Apr 2006 14:28:45 GMT
I got it working.  I was running into the problem with RMI/SureFire
discussed here:

Since my project was in a directory which contained spaces in the path, the
RMI-based test cases failed using M2, but they worked with M1.  Anyway, I
copied the project to a directory which did not contain spaces (and moved my
local repository to a directory which did not contain spaces) and it worked
using M2.  My M1 build works just fine and has for quite some time. 

-----Original Message-----
From: Dennis Lundberg [] 
Sent: Friday, April 14, 2006 10:22 AM
To: Jakarta Commons Developers List
Subject: Re: [all] Maven 1.0 vs. 2.0

James Carman wrote:
> All,
> What's the standard build system for Jakarta Commons right now?  I know
> folks have been trying to move to M2, but is it stable enough and does it
> support all we need currently (like sshdeploy and the like)?  I'd like to
> move Commons Proxy to the proper, but my M2 build isn't quite working the
> way I want it.
> James

Previous discussions on this topic can be summarized like this: Until 
Maven 2 is sufficiently stable Commons Proper components should continue 
to use Maven 1. There are experiments going on in the sandbox with Maven 
2 builds with various degrees of success.

For more reading, please see the wiki:
In particular the documents ReleaseShoppingList, CreatingSiteWithMaven2 
and MavenPlugins.

If you need a hand with the Maven 2 build for Commons Proxy, let me know 
what the problem is and I'll see what I can do.

Dennis Lundberg

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message