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 -version
Using Java version: 1.5
Apache Maven 2.1.0-RC3 (r754932; 2009-03-16 17:31:06+0100)
Java version: 1.5.0_16
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x" version: "10.5.6" arch: "i386" Family: "unix"



 cat output.lis | grep blacklist | sort | uniq
[WARNING] The repository url 'http://people.apache.org/repo/m2-ibiblio-rsync-repository/' is invalid - Repository 'apache-ibiblio-rsync' will be blacklisted. [WARNING] The repository url 'http://people.apache.org/repo/m2-incubating-repository' is invalid - Repository 'apache-snapshots' will be blacklisted. [WARNING] The repository url 'http://people.apache.org/repo/m2-incubating-repository/' is invalid - Repository 'apache-incubator' will be blacklisted. [WARNING] The repository url 'http://people.apache.org/repo/m2-snapshot-repository' is invalid - Repository 'apache-snapshots' will be blacklisted. [WARNING] The repository url 'http://people.apache.org/repo/m2-snapshot-repository' is invalid - Repository 'apache.snapshots' will be blacklisted. [WARNING] The repository url 'http://serp.sourceforge.net/m2repo' is invalid - Repository 'serp' will be blacklisted. [WARNING] The repository url 'http://svn.apache.org/maven-snapshot-repository' is invalid - Repository 'apache.snapshots' will be blacklisted.


On 18/03/2009, at 18.26, Arnaud HERITIER wrote:

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 <[email protected]> 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 about StringBuffer.append(..). When I investigated, I found that the problem seems to be coming from cargo's jetty test container, which seems to require JDK
1.5 in order to run.

This isn't a problem with maven; it's a problem with the archetype project.
And, it's happening with Maven 2.0.10 as well.


John Casey wrote:

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 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 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
missing dependency
(org.apache.maven.archetype:archetype-packaging:jar:2.0-alpha-5- SNAPSHOT)

and the following stacktrace :
java.lang.NoSuchMethodError:
java.lang.StringBuffer.append(Ljava/lang/CharSequence;II)Ljava/ lang/StringBuffer;

at org.mortbay.util.URIUtil.compactPath(URIUtil.java:544)
at
org .mortbay .jetty .webapp.WebAppContext.isProtectedTarget(WebAppContext.java:845)

at
org .mortbay .jetty.handler.ContextHandler.handle(ContextHandler.java:724)
at
org .mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java: 405)
at
org .mortbay .jetty .handler .ContextHandlerCollection.handle(ContextHandlerCollection.java: 206)

at
org .mortbay .jetty.handler.HandlerCollection.handle(HandlerCollection.java: 114)

at
org .mortbay .jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at
org .mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java: 505)
at
org.mortbay.jetty.HttpConnection $RequestHandler.headerComplete(HttpConnection.java:829)

at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java: 211) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java: 380)
at
org .mortbay .io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)

at
org.mortbay.thread.QueuedThreadPool $PoolThread.run(QueuedThreadPool.java:488)

[ERROR] The desired archetype does not exist
(org.apache.maven.test:test-project-2:1.0)

But the error is perhaps in a jetty used for integration tests ?
I don't have the time to investigate tonight.

cheers

Arnaud






On Tue, Mar 17, 2009 at 11:35 PM, Arnaud HERITIER <[email protected]
wrote:

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 <[email protected]
wrote:

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 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' support ?

Arnaud

On Mon, Mar 16, 2009 at 5:51 PM, John Casey <[email protected]

wrote:

Okay,


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.org/content/repositories/maven-staging-5078cd01de9bd9/org/apache/maven/apache-maven/2.1.0-RC3/
)

Thanks for your patience.

-john

---------------------------------------------------------------------

To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]




--
Arnaud




--
Arnaud


--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------

To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]




--
Arnaud


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to