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 <aherit...@gmail.com>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 <jdca...@commonjava.org>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 <jdca...@commonjava.org> >>> 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: dev-unsubscr...@maven.apache.org >>>> For additional commands, e-mail: dev-h...@maven.apache.org >>>> >>>> >>>> >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > > > -- > Arnaud > -- Arnaud
