You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by John Casey <jd...@commonjava.org> on 2009/03/16 17:51:16 UTC
[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 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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [PLEASE TEST] Maven 2.1.0-RC3
Posted by "Nord, James" <JN...@nds.com>.
I'm having issues with releasing (but this is not specific to 2.1.0-RC3
and is reproducible on 2.0.10).
(http://jira.codehaus.org/browse/MRELEASE-406) but I am not sure if it
is a fault in core or the release plug-in.
Basically a forked maven process doesn't inherit env vars.
D:\workspaces\svn_all\maven\sandbox\james\buildenvtests\trunk\anothertes
t>set | grep proxyURL
proxyURL=http://nexus/nexus/content/repositories
Settings.xml contains
<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">
<mirrors>
<mirror>
<id>central-mirror</id>
<name>Maven Central [nexus mirror]</name>
<url>${env.proxyURL}/central</url>
<mirrorOf>central</mirrorOf>
</mirror>
</mirrors>
</settings>
mvn -B release:prepare release:perform
<snip>
57K downloaded (maven-scm-provider-svnexe-1.1.jar)
Downloading:
http://nexus/nexus/content/repositories/central/org/apache/maven/scm/mav
en-scm-provider-synergy/1.1/maven-scm-provider-synergy-1.1.jar
49K downloaded (maven-scm-provider-synergy-1.1.jar)
[INFO] [release:prepare]
[INFO] Resuming release from phase 'run-preparation-goals'
[INFO] Executing goals 'clean verify'...
[INFO] [INFO] Scanning for projects...
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] [INFO] Building Another test project
[INFO] [INFO] task-segment: [clean, verify]
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] Downloading:
${env.proxyURL}/central/org/apache/maven/plugins/maven-clean-plugin/2.2/
maven-clean-plugin-2.2.pom
[INFO] [INFO] Unable to find resource
'org.apache.maven.plugins:maven-clean-plugin:pom:2.2' in repository
central (http://repo1.maven.org/maven2)
[INFO] Downloading:
${env.proxyURL}/central/org/apache/maven/plugins/maven-clean-plugin/2.2/
maven-clean-plugin-2.2.pom
[INFO] [INFO] Unable to find resource
'org.apache.maven.plugins:maven-clean-plugin:pom:2.2' in repository
central (http://repo1.maven.org/maven2)
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
------------------------------------------------------------------------
[INFO] [INFO] Error building POM (may not be this project's POM).
> -----Original Message-----
> From: Jochen Wiedmann [mailto:jochen.wiedmann@gmail.com]
> Sent: 16 March 2009 20:40
> To: Maven Developers List
> Subject: Re: [PLEASE TEST] Maven 2.1.0-RC3
>
> On Mon, Mar 16, 2009 at 5:51 PM, John Casey
> <jd...@commonjava.org> 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.org/content/repositories/maven-staging-5078
> > cd01de9bd9/org/apache/maven/apache-maven/2.1.0-RC3/)
>
> Looks good on my corporate builds.
>
> Jochen
>
>
> --
> I have always wished for my computer to be as easy to use as
> my telephone; my wish has come true because I can no longer
> figure out how to use my telephone.
>
> -- (Bjarne Stroustrup,
> http://www.research.att.com/~bs/bs_faq.html#really-say-that
> My guess: Nokia E50)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
>
**************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the postmaster@nds.com and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.
To protect the environment please do not print this e-mail unless necessary.
NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC3
Posted by Piotr Tabor <pi...@gmail.com>.
Jochen Wiedmann pisze:
> On Mon, Mar 16, 2009 at 5:51 PM, John Casey <jd...@commonjava.org> 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.org/content/repositories/maven-staging-5078cd01de9bd9/org/apache/maven/apache-maven/2.1.0-RC3/)
>>
>
> Looks good on my corporate builds.
>
No problem here with this version. Two complicated projects (50+
subprojects) works great.
Regards,
Piotr Tabor
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC3
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Mon, Mar 16, 2009 at 5:51 PM, John Casey <jd...@commonjava.org> 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.org/content/repositories/maven-staging-5078cd01de9bd9/org/apache/maven/apache-maven/2.1.0-RC3/)
Looks good on my corporate builds.
Jochen
--
I have always wished for my computer to be as easy to use as my
telephone; my wish has come true because I can no longer figure out
how to use my telephone.
-- (Bjarne Stroustrup,
http://www.research.att.com/~bs/bs_faq.html#really-say-that
My guess: Nokia E50)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re : [PLEASE TEST] Maven 2.1.0-RC3
Posted by Julien HENRY <he...@yahoo.fr>.
Works fine for me.
Good job!
----- Message d'origine ----
De : John Casey <jd...@commonjava.org>
À : Maven Developers List <de...@maven.apache.org>
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 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-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC3
Posted by Anders Kristian Andersen <an...@gmail.com>.
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 <jd...@commonjava.org>
> 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 <aheritier@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 <jdcasey@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 <jdcasey@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-unsubscribe@maven.apache.org
>>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Arnaud
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Arnaud
>>>>>>
>>>>>
>>>>> --
>>>>> Brett Porter
>>>>> brett@apache.org
>>>>> http://blogs.exist.com/bporter/
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>>
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> Arnaud
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC3
Posted by Arnaud HERITIER <ah...@gmail.com>.
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 <jd...@commonjava.org> 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 <aheritier@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 <jdcasey@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 <jdcasey@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-unsubscribe@maven.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Arnaud
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Arnaud
>>>>>
>>>>
>>>> --
>>>> Brett Porter
>>>> brett@apache.org
>>>> http://blogs.exist.com/bporter/
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Arnaud
Re: [PLEASE TEST] Maven 2.1.0-RC3
Posted by John Casey <jd...@commonjava.org>.
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
>>>> <ah...@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
>>>>> <jd...@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 <jd...@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-unsubscribe@maven.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Arnaud
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Arnaud
>>>
>>> --
>>> Brett Porter
>>> brett@apache.org
>>> http://blogs.exist.com/bporter/
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC3
Posted by John Casey <jd...@commonjava.org>.
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
>>> <ah...@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
>>>> <jd...@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 <jd...@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-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Arnaud
>>>>
>>>
>>>
>>>
>>> --
>>> Arnaud
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://blogs.exist.com/bporter/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC3
Posted by John Casey <jd...@commonjava.org>.
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
>> <ah...@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
>>> <jd...@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 <jd...@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-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Arnaud
>>>
>>
>>
>>
>> --
>> Arnaud
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC3
Posted by Brett Porter <br...@apache.org>.
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
> <ah...@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
>> <jd...@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
>>>> <jd...@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-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>>
>> --
>> Arnaud
>>
>
>
>
> --
> Arnaud
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC3
Posted by Arnaud HERITIER <ah...@gmail.com>.
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 <ah...@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 <jd...@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 <jd...@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-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> Arnaud
>
--
Arnaud
Re: [PLEASE TEST] Maven 2.1.0-RC3
Posted by Arnaud HERITIER <ah...@gmail.com>.
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 <jd...@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 <jd...@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-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>>
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Arnaud
Re: [PLEASE TEST] Maven 2.1.0-RC3
Posted by John Casey <jd...@commonjava.org>.
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 <jd...@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC3
Posted by Arnaud HERITIER <ah...@gmail.com>.
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 <jd...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Arnaud
RE: [PLEASE TEST] Maven 2.1.0-RC3
Posted by Steve Ariantaj <st...@tvworks.com>.
Passed tests on our projects.
-----Original Message-----
From: John Casey [mailto:jdcasey@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 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-5078cd
01de9bd9/org/apache/maven/apache-maven/2.1.0-RC3/)
Thanks for your patience.
-john
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org