On 10-Feb-09, at 8:56 AM, Wendy Smoak wrote:
On Tue, Feb 10, 2009 at 6:26 AM, Paul Benedict
wrote:
Will the download page be updated to contain this? 2.1-M1 is
there ...
kind of makes sense to me 3.0 should be there too.
Jason mentioned he doesn't recommend anyone try it just yet, so I
w
Not until we think it's ready for a wider audience. The criterion for
that will be we can't find any projects that won't run on 3.0. The
point at which that happens it will be generally worth people trying
it. Before that I honestly think it's a waste of their time. As the
alphas proceed to
Probably but I'm just leaving all the crap there that the release
produces. I'll figure out why the tool is producing that or what
happened and fix that.
The apache-maven-* bits should be excluded but I'm not sure what made
the empty directories. That why we're going to have a _lot_ of alph
On Tue, Feb 10, 2009 at 6:26 AM, Paul Benedict wrote:
> Will the download page be updated to contain this? 2.1-M1 is there ...
> kind of makes sense to me 3.0 should be there too.
Jason mentioned he doesn't recommend anyone try it just yet, so I
wouldn't put it on the download page which is inten
Will the download page be updated to contain this? 2.1-M1 is there ...
kind of makes sense to me 3.0 should be there too.
Paul
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@m
Jason van Zyl wrote:
http://www.apache.org/dist/maven/binaries/
There are some files that could probably be deleted. E.g. an empty
3.0-alpha-2 directory, apache-maven-3.0-alpha-2.pom* and
apache-maven-3.0-alpha-2.jar*.
Benjamin
Another quiet release as we build up the integration tests and flush
out regressions. Not recommending this to anyone but the masochists,
but here it is:
http://www.apache.org/dist/maven/binaries/
There were 48 issues resolved, and you can see them here:
http://jira.codehaus.org/secure/Issu
