Re: Maven 3 alpha status

[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 ? ;)

2010/1/29 Stephane Nicoll <stephane.nic...@gmail.com>

> Which bug are your talking about? Have you filled something in Jira?
>
> S.
>
> On Fri, Jan 29, 2010 at 12:08 PM, Julien HENRY <henr...@yahoo.fr> 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 no reason that the ear plugin "see" this dependency.
> > As I read Maven 3 is much more precise dealing with plugin classpath and
> > dependencies, I asked the project leader to try with Maven 3 alpha 6.
> > Hourra! It worked fine.
> >
> > So I told the project to migrate to Maven 3 but the project leader was
> > reluctant as it is flagged as "alpha".
> >
> > As it seems many Maven guys say Maven 3 alpha 6 is much better than Maven
> > 2.2.1, could you please for next release use a version with a "higher"
> > qualifier that will not afraid corporate people. IMHO "beta" will face
> the
> > same issue, so I suggest "rc" or something like that.
> >
> > Best regards,
> >
> > Julien
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
>
> --
> Large Systems Suck: This rule is 100% transitive. If you build one, you
> suck" -- S.Yegge
>