Thanks John. I will try next RC and comment in Jira issue if there is still a
problem.
- Message d'origine
De : John Casey <[EMAIL PROTECTED]>
À : Maven Developers List
Envoyé le : Vendredi, 18 Juillet 2008, 17h18mn 53s
Objet : Re: Re : [PLEASE TEST] Maven 2.0.10-RC1
Okay, I've duplicated the problem, and generated a simple test case to
replicate it separately from the JWebUnit project, so we can create an
integration test. The JIRA issue is:
http://jira.codehaus.org/browse/MNG-3671
I have a fix for this issue (I believe), but still need to formalize the
I'll give it a try today and see if I can reproduce the problem. Then,
we should file a JIRA ticket so it shows up on the release notes, and
I'll fix it.
Thanks for testing!
-john
Julien HENRY wrote:
Hi John,
I can't manage to build JWebUnit anymore with 2.0.10-RC1. One of my module is
dep
Hi John,
I can't manage to build JWebUnit anymore with 2.0.10-RC1. One of my module is
depending on the other one using this syntax:
net.sourceforge.jwebunit
jwebunit-webtestcase-generator
${pom.version}
Found it and fixed it. Thanks for testing!
Henrique Prange wrote:
Hi John,
I've tried Maven 2.0.10-RC1 with one of my projects and got a
NullPointerException while resolving dependencies (below is the stack
trace). It works using Maven 2.0.9.
Should I file a bug on Jira with fix-for 2.0.10?
Hi John,
I've tried Maven 2.0.10-RC1 with one of my projects and got a
NullPointerException while resolving dependencies (below is the stack
trace). It works using Maven 2.0.9.
Should I file a bug on Jira with fix-for 2.0.10?
Cheers,
Henrique
hprange:pas-human-resources-model hprange$ mvn
too. I think for this purpose it's not needed.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Paul Benedict
Sent: Wednesday, July 16, 2008 8:18 PM
To: Maven Developers List
Subject: Re: [PLEASE TEST] Maven 2.0.10-RC1
I do not think it's worth doin
lf Of Paul Benedict
Sent: Wednesday, July 16, 2008 8:18 PM
To: Maven Developers List
Subject: Re: [PLEASE TEST] Maven 2.0.10-RC1
I do not think it's worth doing.
RCs for Maven are not used like they are for at other projects, e.g.,
the
Spring Framework. Spring uses each RC to apply about 10
at the
> > >> end are complete and under a single version.
> > >>
> > >> -Original Message-
> > >> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > >> Sent: Wednesday, July 16, 2008 9:11 AM
> > >> To: Maven Developers List
l-08, at 10:34 AM, Brian E. Fox wrote:
> >
> >> I would just continue to use 2.0.10, that way the release notes at the
> >> end are complete and under a single version.
> >>
> >> -Original Message-
> >> From: Jason van Zyl [mailto:[
ednesday, July 16, 2008 9:11 AM
>> To: Maven Developers List
>> Subject: Re: [PLEASE TEST] Maven 2.0.10-RC1
>>
>> John, maybe a new version in JIRA to help track issues/regressions for
>> the RC cycle would help. Brian ended up doing 9 RCs so I'm sure we'll
&
This is fixed. I'm formalizing things and adding an integration test now.
Arnaud HERITIER wrote:
Done.
http://jira.codehaus.org/browse/MNG-3667
cheers,
arnaud
On Wed, Jul 16, 2008 at 4:16 PM, John Casey <[EMAIL PROTECTED]> wrote:
Please file with fix-for of 2.0.10, with that test case if y
Previously in wagon, the "transferError" event was used haphazardly
(ie, not for all errors, inconsistently across providers, etc). It's
use is now uniform.
However, it is firing for all exceptions (including not found and
authorization failures). On second thought that is probably not the
Done.
http://jira.codehaus.org/browse/MNG-3667
cheers,
arnaud
On Wed, Jul 16, 2008 at 4:16 PM, John Casey <[EMAIL PROTECTED]> wrote:
> Please file with fix-for of 2.0.10, with that test case if you have it. :-)
>
> Thanks,
>
> -john
>
> Arnaud HERITIER wrote:
>
>> With RC1, maven tries to down
complete and under a single version.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 16, 2008 9:11 AM
To: Maven Developers List
Subject: Re: [PLEASE TEST] Maven 2.0.10-RC1
John, maybe a new version in JIRA to help track issues/regressions for
the RC cycle
I would just continue to use 2.0.10, that way the release notes at the
end are complete and under a single version.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 16, 2008 9:11 AM
To: Maven Developers List
Subject: Re: [PLEASE TEST] Maven 2.0.10
Please file with fix-for of 2.0.10, with that test case if you have it. :-)
Thanks,
-john
Arnaud HERITIER wrote:
With RC1, maven tries to download this dependency
org/apache/ws/commons/XmlSchema/SNAPSHOT/XmlSchema-SNAPSHOT.jar whereas with
2.0.9 it retreives the version 1.1.
What I have is a p
Please file this with fix-for of 2.0.10. I'll take a look.
-john
nicolas de loof wrote:
Running mvn eclipse:eclipse on my project dump many stacktrace on the
console :
Downloading:
http://sai1rennes:/archiva/repository/releases/org/jmock/jmock/2.4.0/jmock-2.4.0-javadoc.jar
org.apache.maven
Hang on a second though; since we're attempting to release 2.0.10, why
not file the issues under there?
I think I'd rather see that happen, since then the final release notes
for 2.0.10 will incorporate any issues we find along the way.
-john
Jason van Zyl wrote:
John, maybe a new version in
I'll set that up now.
Jason van Zyl wrote:
John, maybe a new version in JIRA to help track issues/regressions for
the RC cycle would help. Brian ended up doing 9 RCs so I'm sure we'll
get close to that again. Especially given what look like fundament
problems with wagon/artifact resolution.
John, maybe a new version in JIRA to help track issues/regressions for
the RC cycle would help. Brian ended up doing 9 RCs so I'm sure we'll
get close to that again. Especially given what look like fundament
problems with wagon/artifact resolution.
On 16-Jul-08, at 8:12 AM, nicolas de loof
With RC1, maven tries to download this dependency
org/apache/ws/commons/XmlSchema/SNAPSHOT/XmlSchema-SNAPSHOT.jar whereas with
2.0.9 it retreives the version 1.1.
What I have is a project with a dependency to
org.codehaus.xfire:xfire-core:1.2.6
In the xfire-core pom we have a dependency to
org.apac
Running mvn eclipse:eclipse on my project dump many stacktrace on the
console :
Downloading:
http://sai1rennes:/archiva/repository/releases/org/jmock/jmock/2.4.0/jmock-2.4.0-javadoc.jar
org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate
resource in repository
at
org
Looks like the 1.1 version of the shade plugin didn't do what I needed
it to WRT avoiding rewriting the Xpp3Dom and/or XmlSerializer classes.
The IT for MNG-3503 is messed up in the RC1 build, so I'll be cutting an
RC2 as soon as I can verify that 1.0 of the shade plugin works (this is
what we
24 matches
Mail list logo
