On Mon, Mar 16, 2009 at 5:51 PM, John Casey wrote:
> It looks like the last known bugs are resolved for 2.1.0. So, let's take
> another look things with RC3, and if everything is clean I'll call a vote in
> the next day or two.
>
> http://tinyurl.com/maven-2-1-0-RC3
> (https://repository.apache.o
Jochen Wiedmann pisze:
On Mon, Mar 16, 2009 at 5:51 PM, John Casey wrote:
It looks like the last known bugs are resolved for 2.1.0. So, let's take
another look things with RC3, and if everything is clean I'll call a vote in
the next day or two.
http://tinyurl.com/maven-2-1-0-RC3
(https://r
Works fine for me.
Good job!
- Message d'origine
De : John Casey
À : Maven Developers List
Envoyé le : Lundi, 16 Mars 2009, 17h51mn 16s
Objet : [PLEASE TEST] Maven 2.1.0-RC3
Okay,
It looks like the last known bugs are resolved for 2.1.0. So, let's take
another look things with RC
-
[INFO] [INFO] Error building POM (may not be this project's POM).
> -Original Message-
> From: Jochen Wiedmann [mailto:jochen.wiedm...@gmail.com]
> Sent: 16 March 2009 20:40
> To: Maven Developers List
> Subject: Re: [PLEASE TEST] Maven 2.1.0-RC3
>
Passed tests on our projects.
-Original Message-
From: John Casey [mailto:jdca...@commonjava.org]
Sent: Monday, March 16, 2009 9:51 AM
To: Maven Developers List
Subject: [PLEASE TEST] Maven 2.1.0-RC3
Okay,
It looks like the last known bugs are resolved for 2.1.0. So, let's take
another
It seems that we aren't checking for Java version used to launch maven
(>=1.5).I made the error to try to launch a build with the RC3 and Java 1.4
and received a method not found error. I quickly found my error but i'm not
sure everyone will think about this.
Perhaps it could save us time of users'
Funny...I've been building these RC's using JDK 1.4 and Maven 2.0.10
(except RC1, which used 2.1.0-M1, IIRC)...I'll see whether I can
reproduce the error. Do you have any idea where your error came from?
-john
Arnaud HERITIER wrote:
It seems that we aren't checking for Java version used to la
I tried to build the archetype sub project with jdk 1.4 / 2.1.0 RC3I can try
to reproduce it. It seems its because I didn't have some SNAPSHOT
dependencies in my local repo.
On Tue, Mar 17, 2009 at 11:30 PM, John Casey wrote:
> Funny...I've been building these RC's using JDK 1.4 and Maven 2.0.1
I reproduced it.The problem seems to be in jetty.
To reproduce : An empty local repo, JDK 1.4, maven 2.1.0-RC3
In archetype/pom.xml you change the maven-parent version to 11 (instead of
11-SNAPSHOT).
You launch a build
When you'll execute tests in "Building Maven Archetype Common" you'll have a
Seems like this would fail on earlier versions as well?
On 18/03/2009, at 9:50 AM, Arnaud HERITIER wrote:
I reproduced it.The problem seems to be in jetty.
To reproduce : An empty local repo, JDK 1.4, maven 2.1.0-RC3
In archetype/pom.xml you change the maven-parent version to 11
(instead of
I've actually had a problem using the archetype plugin with JDK < 1.5
for a couple months now. Are we sure this isn't a problem in 2.0.10 as well?
Brett Porter wrote:
Seems like this would fail on earlier versions as well?
On 18/03/2009, at 9:50 AM, Arnaud HERITIER wrote:
I reproduced it.The
Okay, looks like that problem no longer exists...but I can't get it to
fail at all now.
When you talk about archetype/pom.xml, what do you mean? Are you talking
about building the archetype project itself?
John Casey wrote:
I've actually had a problem using the archetype plugin with JDK < 1.5
When I tried to build the archetype project itself using JDK 1.4, I
found that the unit tests wouldn't run. I got the same missing method
error about StringBuffer.append(..). When I investigated, I found that
the problem seems to be coming from cargo's jetty test container, which
seems to requi
ok thus it was a false alert. I tested with the wrong project ;-)Thanks for
your help.
Arnaud
On Wed, Mar 18, 2009 at 5:30 PM, John Casey wrote:
> When I tried to build the archetype project itself using JDK 1.4, I found
> that the unit tests wouldn't run. I got the same missing method error a
I have tested 2.1.0-RC3 on a larger project that I have build over the
last 6 month using 2.0.9
All features seems to run.
I find it fast
It seems to warn me better etc.
So I find it positive
/Anders
Attached:
1) version
2) some repository blacklistings, they are not all new
$ mvn -versi
15 matches
Mail list logo