Re: Maven 3 alpha status

2010-01-29 Thread Jason van Zyl
On 2010-01-29, at 5:02 PM, Gustavo Hexsel wrote: > Just as a side note: in most projects, alpha implies that changes in > features or public APIs is possible or likely. Maybe it's not the case for > Maven... > From the CLI perspective nothing should change, so from that perspective there is

Re: New Release Tree Maven Module

2010-01-29 Thread Mark Hobson
I'm a little confused as to what this approach involves, as you seem to suggest releasing up the dependency tree from a given leaf project? I'd certainly advocate a release goal to release in the opposite direction, i.e. a project and all its snapshot dependencies down the dependency tree. Mark

Re: Maven 3 alpha status

2010-01-29 Thread Gustavo Hexsel
Just as a side note: in most projects, alpha implies that changes in features or public APIs is possible or likely. Maybe it's not the case for Maven... []s Gus On Fri, Jan 29, 2010 at 7:38 AM, Jason van Zyl wrote: > > On 2010-01-29, at 4:09 PM, nicolas de loof wrote: > > > could we use

Re: Maven 3 alpha status

2010-01-29 Thread Jason van Zyl
On 2010-01-29, at 4:09 PM, nicolas de loof wrote: > could we use "milestone" as names in replacement for "alpha", so that we get > more early-adopter to test the (pre)release and detected regressions ? > > I can understand the difficulty to suggest a build tool with "alpha" in > version name. Wo

Re: Re : Maven 3 alpha status

2010-01-29 Thread Stephane Nicoll
I don't think it will be fixed in Maven 2.2 but as far as the ear plugin is concerned you can workaround it, just declare your zip dependency as provided. The problem here is that your EAR project has a wrong zip dependency with "please bundle it" scope. S. On Fri, Jan 29, 2010 at 4:33 PM, Juli

Re : Maven 3 alpha status

2010-01-29 Thread Julien HENRY
Hi, The bug is something similar to [1] (at leat same error message except the type is xml.zip in my case). The EAR module is building fine alone, but as soon as I launch a full reactor build, the build fails. Running with -X show the dependency is in the EAR plugin classpath but it should not

Re: Maven 3 alpha status

2010-01-29 Thread nicolas de loof
could we use "milestone" as names in replacement for "alpha", so that we get more early-adopter to test the (pre)release and detected regressions ? I can understand the difficulty to suggest a build tool with "alpha" in version name. Would you install Windows 8 alpha on your @work computer ? ;) 2

Re: Maven 3 alpha status

2010-01-29 Thread Stephane Nicoll
Which bug are your talking about? Have you filled something in Jira? S. On Fri, Jan 29, 2010 at 12:08 PM, Julien HENRY wrote: > Hi, > > Yesterday I spend 2 hours fixing a nasty bug with EAR plugin and dependency > with type "xml.zip". This dependency was declared in another module of the > reac

Re: Maven 3 alpha status

2010-01-29 Thread Jason van Zyl
On 2010-01-29, at 12:08 PM, Julien HENRY wrote: > Hi, > > Yesterday I spend 2 hours fixing a nasty bug with EAR plugin and dependency > with type "xml.zip". This dependency was declared in another module of the > reactor, and was a dependency of a plugin (maven-andromda-plugin). So there > is

Maven 3 alpha status

2010-01-29 Thread Julien HENRY
Hi, Yesterday I spend 2 hours fixing a nasty bug with EAR plugin and dependency with type "xml.zip". This dependency was declared in another module of the reactor, and was a dependency of a plugin (maven-andromda-plugin). So there is no reason that the ear plugin "see" this dependency. As I rea

dependencyManagament dependencies within profiles are not activated by settings.xml

2010-01-29 Thread Moser, Christian
Hi Could someone give me a comment to this issue, please? Is it by design or a bug? http://jira.codehaus.org/browse/MNG-4538 Thanks for advice, Christian Moser