Re: Notes from Build Tools BOF at ApacheCon US 2008

2008-11-16 Thread James William Dumay
On Fri, 2008-11-07 at 14:38 -0600, Wendy Smoak wrote: > Surefire fills up /tmp with directories Cargo is notorious for doing this also. It downloads application servers to /tmp/cargo which means it suffers from race conditions with multiple processes starting app servers. James

Re: Notes from Build Tools BOF at ApacheCon US 2008

2008-11-16 Thread Martijn Dashorst
On Sat, Nov 15, 2008 at 2:35 AM, Dan Fabulich <[EMAIL PROTECTED]> wrote: > Wendy Smoak wrote: >> Unit tests run slower in Maven than in Ant >> >> Surefire fills up /tmp with directories > > Are there bugs filed for this? Do we think that the /tmp directories are > the cause of our perf troubles?

[ANN] Maven DOCCK Plugin 1.0 Released

2008-11-16 Thread Dennis Lundberg
The Maven team is pleased to announce the release of the Maven DOCCK Plugin, version 1.0 This plugin checks that a project complies with the Plugin Documentation Standard. http://maven.apache.org/plugins/maven-docck-plugin/ You should specify the version in your project's plugin configuration:

Re: RFC : integration tests

2008-11-16 Thread Benjamin Bentmann
nicolas de loof wrote: maven default lifecycle defines integration-test phase, but AFAIK there is no consensus (yet) on how to use it. Just to mention a related Wiki article where people have previously collected some ideas: http://docs.codehaus.org/display/MAVEN/best+practices+-+testing+str

Re: Version range special cases?

2008-11-16 Thread Hervé BOUTEMY
Le dimanche 16 novembre 2008, Dave Syer a écrit : > Hervé BOUTEMY wrote: > > [1] http://docs.codehaus.org/display/MAVEN/Versioning > > I didn't see any reference there to special qualifiers. See "Proposal" section, "strings are checked for well-known qualifiers and the qualifier ordering is used

Re: RFC : integration tests

2008-11-16 Thread Rémy Sanlaville
Hi Nicolas, I agree that integration-test is not enough support with maven. I thought that src/it/ and target/it was the original convention (even if it is not really used because of the lack of integration with maven 2.0.x). It would be really nice to have a better and standard support for inte

[RESULT] [VOTE] Release Maven Docck Plugin version 1.0

2008-11-16 Thread Dennis Lundberg
Hi, The vote has passed with the following result : +1 (binding): Olivier Lamy, Dennis Lundberg, Hervé Boutemy +1 (non binding): Raphaël Piéroni I will move the artifacts to central repo. Dennis Lundberg wrote: > Hi, > > We solved 4 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?p

Re: svn commit: r717964 - in /maven/components/trunk: ./ maven-compat/ maven-core/src/main/java/org/apache/maven/execution/ maven-core/src/main/java/org/apache/maven/lifecycle/ maven-core/src/main/jav

2008-11-16 Thread Benjamin Bentmann
Jason van Zyl wrote: Fixed, sorry about that. A build with Maven now works Hm, I still get the missing dependency error for plexus-container-default:jar:1.0-beta-2-SNAPSHOT when doing "mvn clean package" on trunk. Either the repo URL in the POM needs to be updated or the snapshots are sim

Re: Version range special cases?

2008-11-16 Thread Michael McCallum
On Mon, 17 Nov 2008 00:43:03 Dave Syer wrote: > > Michael McCallum-3 wrote: > > > > just start at 2.1 and everything just works and makes sense... > > > > Sorry, not to me, and not to anyone I know who uses version ranges. The works or make sense ;-) > OSGi version conventions always used to

Re: svn commit: r717964 - in /maven/components/trunk: ./ maven-compat/ maven-core/src/main/java/org/apache/maven/execution/ maven-core/src/main/java/org/apache/maven/lifecycle/ maven-core/src/main/jav

2008-11-16 Thread Jason van Zyl
Fixed, sorry about that. A build with Maven now works, but I still have a problem with the bootstrap. Cleaning up all the realm lookups revealed a nasty bug in ClassWorlds which I'm fixing now. On 16-Nov-08, at 5:12 AM, Benjamin Bentmann wrote: Hi Jason, Author: jvanzyl Date: Sat Nov 15

RFC : integration tests

2008-11-16 Thread nicolas de loof
Hi, First of all, please don't blame me for my horrible english. I'm french, and french guys are known for beeing poor foreign language speackers... maven default lifecycle defines integration-test phase, but AFAIK there is no consensus (yet) on how to use it. Some wiki doc help to setup a maven/

Re: Version range special cases?

2008-11-16 Thread Dave Syer
Michael McCallum-3 wrote: > > just start at 2.1 and everything just works and makes sense... > Sorry, not to me, and not to anyone I know who uses version ranges. The OSGi version conventions always used to annoy me. Now I've found something even worse. Why don't we just adopt the same rule

Re: svn commit: r717964 - in /maven/components/trunk: ./ maven-compat/ maven-core/src/main/java/org/apache/maven/execution/ maven-core/src/main/java/org/apache/maven/lifecycle/ maven-core/src/main/jav

2008-11-16 Thread Benjamin Bentmann
Hi Jason, Author: jvanzyl Date: Sat Nov 15 18:38:13 2008 New Revision: 717964 URL: http://svn.apache.org/viewvc?rev=717964&view=rev Log: o use the class lookup method which will now automatically partition lookups based on the class submitted by: Dain Sundstrom [...] Modified: maven/compon

Re: Version range special cases?

2008-11-16 Thread Michael McCallum
On Sun, 16 Nov 2008 21:51:18 Dave Syer wrote: > > Hervé BOUTEMY wrote: > > > > [1] http://docs.codehaus.org/display/MAVEN/Versioning > > > > I didn't see any reference there to special qualifiers. But anyway, how > does it make sense for [1.0.0,2.0.0) (with an *exclusive* upper bound of > 2.0.

Re: Version range special cases?

2008-11-16 Thread Dave Syer
Hervé BOUTEMY wrote: > > [1] http://docs.codehaus.org/display/MAVEN/Versioning > I didn't see any reference there to special qualifiers. But anyway, how does it make sense for [1.0.0,2.0.0) (with an *exclusive* upper bound of 2.0.0) to include anything from the 2.0.0. branch? I don't think