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 2008/07/16 00:23:46 UTC
[PLEASE TEST] Maven 2.0.10-RC1
Hi again,
As promised, I've staged the first release candidate for Maven 2.0.10 here:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/
The issues resolved for this release (so far) are here:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112
If you look at the Road Map view in JIRA, you'll notice that MNG-3639 is
still open. This is because one of the possible solutions to this issue
- and the only one that the Maven project really has control over -
depends on re-releasing a new version of commons-build-plugin that will
depend on the eventual 2.0.10 version of maven-script-ant.
Please, try out this release candidate and let me know what's broken!
Once things stabilize, I'll kick it out to the users to have a go, then
if it's still stable after that (or, whatever RC we find is stable at
that point), I'll call a vote to release. At that point, I'll run a new
build to generate artifacts without the RC# suffix in the version.
Thanks!
-john
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC1
Posted by John Casey <jd...@commonjava.org>.
couldn't agree more. I think we'll do fine with a date filter if we
really want to know how many things broke after the first RC was cut.
I've fixed two issues since then, and we're waiting to see what happens
with the shade plugin to fix a third...not a huge list to justify a
whole new version in JIRA.
IMO the overhead involved in juggling all those versions isn't worth it.
-john
Brian E. Fox wrote:
> Yes, at first I thought, duh that seems so obvious. But then we'd need
> to preserve all those versions and they would also pollute the fixed in
> drop down too. I think for this purpose it's not needed.
>
> -----Original Message-----
> From: paulus.benedictus@gmail.com [mailto:paulus.benedictus@gmail.com]
> 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 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 100 new issues to
> bring
> the product to a "feature complete" stage. At Maven, the use of RC is to
> eliminate regressions after features are complete.
>
> If you saw how 2.0.9 went, typically only one issue separated one RC
> from
> another. If the above point didn't sell, I further add It wouldn't be
> worth
> the maintenance for single issues.
>
> Paul
>
> On Wed, Jul 16, 2008 at 7:08 PM, Arnaud HERITIER <ah...@gmail.com>
> wrote:
>
>> It is so much logic that I didn' think about it
>> What do you think guys ?
>> It seems to be the good idea ?
>>
>> Arnaud
>>
>> On Thu, Jul 17, 2008 at 12:37 AM, Samuel Le Berrigaud
> <samuel.lb@gmail.com
>> wrote:
>>
>>> Hi all,
>>> if you want to have both you surely could.
>>>
>>> Why not adding the 2.0.10 RC1 version to Jira and any issue that is
>>> found in the RC1 would have its affected version field set to 2.0.10
>>> RC1 and the fix for to 2.0.10. That you get the nice release notes
> and
>>> the metrics of what was found in the RC.
>>>
>>> What do you think?
>>>
>>> SaM
>>>
>>> On Thu, Jul 17, 2008 at 12:40 AM, Jason van Zyl <ja...@maven.org>
> wrote:
>>>> Fair enough, I was just trying to get some metrics around what
> surfaces
>>>> after we call the RC, but we could probably do that if we noted
> the
>> date
>>> as
>>>> a filter.
>>>>
>>>> On 16-Jul-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:jason@maven.org]
>>>>> 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 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 wrote:
>>>>>
>>>>>> Running mvn eclipse:eclipse on my project dump many stacktrace
> on the
>>>>>> console :
>>>>>>
>>>>>> Downloading:
>>>>>>
> http://sai1rennes:8888/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
>>>>>> .apache
>>>>>> .maven
>>>>>> .wagon
>>>>>> .providers
>>>>>>
> .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:
>>>>>> 132)
>>>>>> ...
>>>>>>
>>>>>>
>>>>>> The requested artifact is not present in the repo, but this is
> not
>>>>>> blocker
>>>>>> and maven 2.0.9 does not dump such errors.
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2008/7/16 John Casey <jd...@commonjava.org>:
>>>>>>
>>>>>>> Hi again,
>>>>>>>
>>>>>>> As promised, I've staged the first release candidate for Maven
>>>>>>> 2.0.10 here:
>>>>>>>
>>>>>>>
>>>>>>>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apac
> <http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/a
> pac>
>> <
>>
> http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/ap
> ac
>>>>> he/maven/apache-maven/2.0.10-RC1/
>>>>> <
> http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/a
>>>>> pache/maven/apache-maven/2.0.10-RC1/
>>>>>>> The issues resolved for this release (so far) are here:
>>>>>>>
>>>>>>>
>>>>>>>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleNa
>>>>> me=Html&version=14112
>>>>>>> If you look at the Road Map view in JIRA, you'll notice that
>>>>>>> MNG-3639 is
>>>>>>> still open. This is because one of the possible solutions to
> this
>>>>>>> issue -
>>>>>>> and the only one that the Maven project really has control over
> -
>>>>>>> depends on
>>>>>>> re-releasing a new version of commons-build-plugin that will
> depend
>>>>>>> on the
>>>>>>> eventual 2.0.10 version of maven-script-ant.
>>>>>>>
>>>>>>> Please, try out this release candidate and let me know what's
>>>>>>> broken! Once
>>>>>>> things stabilize, I'll kick it out to the users to have a go,
> then
>>>>>>> if it's
>>>>>>> still stable after that (or, whatever RC we find is stable at
> that
>>>>>>> point),
>>>>>>> I'll call a vote to release. At that point, I'll run a new
> build to
>>>>>>> generate
>>>>>>> artifacts without the RC# suffix in the version.
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> -john
>>>>>>>
>>>>>>> --
>>>>>>> John Casey
>>>>>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>>>>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>>>>>
>>>>>>>
>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jason
>>>>>
>>>>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> Founder, Apache Maven
>>>>> jason at sonatype dot com
>>>>> ----------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>>
> ---------------------------------------------------------------------
>>>>> 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
>>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder, Apache Maven
>>>> jason at sonatype dot com
>>>> ----------------------------------------------------------
>>>>
>>>> We all have problems. How we deal with them is a measure of our
> worth.
>>>> -- Unknown
>>>>
>>>>
>>>>
> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Samuel Le Berrigaud
>>>
>>>
> ---------------------------------------------------------------------
>>> 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
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [PLEASE TEST] Maven 2.0.10-RC1
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Yes, at first I thought, duh that seems so obvious. But then we'd need
to preserve all those versions and they would also pollute the fixed in
drop down too. I think for this purpose it's not needed.
-----Original Message-----
From: paulus.benedictus@gmail.com [mailto:paulus.benedictus@gmail.com]
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 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 100 new issues to
bring
the product to a "feature complete" stage. At Maven, the use of RC is to
eliminate regressions after features are complete.
If you saw how 2.0.9 went, typically only one issue separated one RC
from
another. If the above point didn't sell, I further add It wouldn't be
worth
the maintenance for single issues.
Paul
On Wed, Jul 16, 2008 at 7:08 PM, Arnaud HERITIER <ah...@gmail.com>
wrote:
> It is so much logic that I didn' think about it
> What do you think guys ?
> It seems to be the good idea ?
>
> Arnaud
>
> On Thu, Jul 17, 2008 at 12:37 AM, Samuel Le Berrigaud
<samuel.lb@gmail.com
> >
> wrote:
>
> > Hi all,
> > if you want to have both you surely could.
> >
> > Why not adding the 2.0.10 RC1 version to Jira and any issue that is
> > found in the RC1 would have its affected version field set to 2.0.10
> > RC1 and the fix for to 2.0.10. That you get the nice release notes
and
> > the metrics of what was found in the RC.
> >
> > What do you think?
> >
> > SaM
> >
> > On Thu, Jul 17, 2008 at 12:40 AM, Jason van Zyl <ja...@maven.org>
wrote:
> > > Fair enough, I was just trying to get some metrics around what
surfaces
> > > after we call the RC, but we could probably do that if we noted
the
> date
> > as
> > > a filter.
> > >
> > > On 16-Jul-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:jason@maven.org]
> > >> 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 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 wrote:
> > >>
> > >>> Running mvn eclipse:eclipse on my project dump many stacktrace
on the
> > >>> console :
> > >>>
> > >>> Downloading:
> > >>>
http://sai1rennes:8888/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
> > >>> .apache
> > >>> .maven
> > >>> .wagon
> > >>> .providers
> > >>>
.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:
> > >>> 132)
> > >>> ...
> > >>>
> > >>>
> > >>> The requested artifact is not present in the repo, but this is
not
> > >>> blocker
> > >>> and maven 2.0.9 does not dump such errors.
> > >>>
> > >>>
> > >>>
> > >>> 2008/7/16 John Casey <jd...@commonjava.org>:
> > >>>
> > >>>> Hi again,
> > >>>>
> > >>>> As promised, I've staged the first release candidate for Maven
> > >>>> 2.0.10 here:
> > >>>>
> > >>>>
> > >>>>
> > >>
> >
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apac
<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/a
pac>
> <
>
http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/ap
ac
> >
> > >> he/maven/apache-maven/2.0.10-RC1/
> > >>>>
> > >> <
> >
http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/a
> > >> pache/maven/apache-maven/2.0.10-RC1/
> > >>>>>
> > >>>>
> > >>>> The issues resolved for this release (so far) are here:
> > >>>>
> > >>>>
> > >>>>
> > >>
> >
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleNa
> > >> me=Html&version=14112
> > >>>>
> > >>>> If you look at the Road Map view in JIRA, you'll notice that
> > >>>> MNG-3639 is
> > >>>> still open. This is because one of the possible solutions to
this
> > >>>> issue -
> > >>>> and the only one that the Maven project really has control over
-
> > >>>> depends on
> > >>>> re-releasing a new version of commons-build-plugin that will
depend
> > >>>> on the
> > >>>> eventual 2.0.10 version of maven-script-ant.
> > >>>>
> > >>>> Please, try out this release candidate and let me know what's
> > >>>> broken! Once
> > >>>> things stabilize, I'll kick it out to the users to have a go,
then
> > >>>> if it's
> > >>>> still stable after that (or, whatever RC we find is stable at
that
> > >>>> point),
> > >>>> I'll call a vote to release. At that point, I'll run a new
build to
> > >>>> generate
> > >>>> artifacts without the RC# suffix in the version.
> > >>>>
> > >>>> Thanks!
> > >>>>
> > >>>> -john
> > >>>>
> > >>>> --
> > >>>> John Casey
> > >>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> > >>>> Blog: http://www.ejlife.net/blogs/buildchimp/
> > >>>>
> > >>>>
> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >>>> For additional commands, e-mail: dev-help@maven.apache.org
> > >>>>
> > >>>>
> > >>
> > >> Thanks,
> > >>
> > >> Jason
> > >>
> > >> ----------------------------------------------------------
> > >> Jason van Zyl
> > >> Founder, Apache Maven
> > >> jason at sonatype dot com
> > >> ----------------------------------------------------------
> > >>
> > >>
> > >>
> > >>
---------------------------------------------------------------------
> > >> 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
> > >>
> > >
> > > Thanks,
> > >
> > > Jason
> > >
> > > ----------------------------------------------------------
> > > Jason van Zyl
> > > Founder, Apache Maven
> > > jason at sonatype dot com
> > > ----------------------------------------------------------
> > >
> > > We all have problems. How we deal with them is a measure of our
worth.
> > >
> > > -- Unknown
> > >
> > >
> > >
---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> >
> >
> > --
> > Samuel Le Berrigaud
> >
> >
---------------------------------------------------------------------
> > 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.0.10-RC1
Posted by Paul Benedict <pb...@apache.org>.
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 100 new issues to bring
the product to a "feature complete" stage. At Maven, the use of RC is to
eliminate regressions after features are complete.
If you saw how 2.0.9 went, typically only one issue separated one RC from
another. If the above point didn't sell, I further add It wouldn't be worth
the maintenance for single issues.
Paul
On Wed, Jul 16, 2008 at 7:08 PM, Arnaud HERITIER <ah...@gmail.com>
wrote:
> It is so much logic that I didn' think about it
> What do you think guys ?
> It seems to be the good idea ?
>
> Arnaud
>
> On Thu, Jul 17, 2008 at 12:37 AM, Samuel Le Berrigaud <samuel.lb@gmail.com
> >
> wrote:
>
> > Hi all,
> > if you want to have both you surely could.
> >
> > Why not adding the 2.0.10 RC1 version to Jira and any issue that is
> > found in the RC1 would have its affected version field set to 2.0.10
> > RC1 and the fix for to 2.0.10. That you get the nice release notes and
> > the metrics of what was found in the RC.
> >
> > What do you think?
> >
> > SaM
> >
> > On Thu, Jul 17, 2008 at 12:40 AM, Jason van Zyl <ja...@maven.org> wrote:
> > > Fair enough, I was just trying to get some metrics around what surfaces
> > > after we call the RC, but we could probably do that if we noted the
> date
> > as
> > > a filter.
> > >
> > > On 16-Jul-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:jason@maven.org]
> > >> 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 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 wrote:
> > >>
> > >>> Running mvn eclipse:eclipse on my project dump many stacktrace on the
> > >>> console :
> > >>>
> > >>> Downloading:
> > >>> http://sai1rennes:8888/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
> > >>> .apache
> > >>> .maven
> > >>> .wagon
> > >>> .providers
> > >>> .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:
> > >>> 132)
> > >>> ...
> > >>>
> > >>>
> > >>> The requested artifact is not present in the repo, but this is not
> > >>> blocker
> > >>> and maven 2.0.9 does not dump such errors.
> > >>>
> > >>>
> > >>>
> > >>> 2008/7/16 John Casey <jd...@commonjava.org>:
> > >>>
> > >>>> Hi again,
> > >>>>
> > >>>> As promised, I've staged the first release candidate for Maven
> > >>>> 2.0.10 here:
> > >>>>
> > >>>>
> > >>>>
> > >>
> > http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apac<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apac>
> <
> http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apac
> >
> > >> he/maven/apache-maven/2.0.10-RC1/
> > >>>>
> > >> <
> > http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/a
> > >> pache/maven/apache-maven/2.0.10-RC1/
> > >>>>>
> > >>>>
> > >>>> The issues resolved for this release (so far) are here:
> > >>>>
> > >>>>
> > >>>>
> > >>
> > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleNa
> > >> me=Html&version=14112
> > >>>>
> > >>>> If you look at the Road Map view in JIRA, you'll notice that
> > >>>> MNG-3639 is
> > >>>> still open. This is because one of the possible solutions to this
> > >>>> issue -
> > >>>> and the only one that the Maven project really has control over -
> > >>>> depends on
> > >>>> re-releasing a new version of commons-build-plugin that will depend
> > >>>> on the
> > >>>> eventual 2.0.10 version of maven-script-ant.
> > >>>>
> > >>>> Please, try out this release candidate and let me know what's
> > >>>> broken! Once
> > >>>> things stabilize, I'll kick it out to the users to have a go, then
> > >>>> if it's
> > >>>> still stable after that (or, whatever RC we find is stable at that
> > >>>> point),
> > >>>> I'll call a vote to release. At that point, I'll run a new build to
> > >>>> generate
> > >>>> artifacts without the RC# suffix in the version.
> > >>>>
> > >>>> Thanks!
> > >>>>
> > >>>> -john
> > >>>>
> > >>>> --
> > >>>> John Casey
> > >>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> > >>>> Blog: http://www.ejlife.net/blogs/buildchimp/
> > >>>>
> > >>>>
> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >>>> For additional commands, e-mail: dev-help@maven.apache.org
> > >>>>
> > >>>>
> > >>
> > >> Thanks,
> > >>
> > >> Jason
> > >>
> > >> ----------------------------------------------------------
> > >> Jason van Zyl
> > >> Founder, Apache Maven
> > >> jason at sonatype dot com
> > >> ----------------------------------------------------------
> > >>
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> 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
> > >>
> > >
> > > Thanks,
> > >
> > > Jason
> > >
> > > ----------------------------------------------------------
> > > Jason van Zyl
> > > Founder, Apache Maven
> > > jason at sonatype dot com
> > > ----------------------------------------------------------
> > >
> > > We all have problems. How we deal with them is a measure of our worth.
> > >
> > > -- Unknown
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> >
> >
> > --
> > Samuel Le Berrigaud
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
Re: [PLEASE TEST] Maven 2.0.10-RC1
Posted by Arnaud HERITIER <ah...@gmail.com>.
It is so much logic that I didn' think about it
What do you think guys ?
It seems to be the good idea ?
Arnaud
On Thu, Jul 17, 2008 at 12:37 AM, Samuel Le Berrigaud <sa...@gmail.com>
wrote:
> Hi all,
> if you want to have both you surely could.
>
> Why not adding the 2.0.10 RC1 version to Jira and any issue that is
> found in the RC1 would have its affected version field set to 2.0.10
> RC1 and the fix for to 2.0.10. That you get the nice release notes and
> the metrics of what was found in the RC.
>
> What do you think?
>
> SaM
>
> On Thu, Jul 17, 2008 at 12:40 AM, Jason van Zyl <ja...@maven.org> wrote:
> > Fair enough, I was just trying to get some metrics around what surfaces
> > after we call the RC, but we could probably do that if we noted the date
> as
> > a filter.
> >
> > On 16-Jul-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:jason@maven.org]
> >> 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 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 wrote:
> >>
> >>> Running mvn eclipse:eclipse on my project dump many stacktrace on the
> >>> console :
> >>>
> >>> Downloading:
> >>> http://sai1rennes:8888/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
> >>> .apache
> >>> .maven
> >>> .wagon
> >>> .providers
> >>> .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:
> >>> 132)
> >>> ...
> >>>
> >>>
> >>> The requested artifact is not present in the repo, but this is not
> >>> blocker
> >>> and maven 2.0.9 does not dump such errors.
> >>>
> >>>
> >>>
> >>> 2008/7/16 John Casey <jd...@commonjava.org>:
> >>>
> >>>> Hi again,
> >>>>
> >>>> As promised, I've staged the first release candidate for Maven
> >>>> 2.0.10 here:
> >>>>
> >>>>
> >>>>
> >>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apac<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apac>
> >> he/maven/apache-maven/2.0.10-RC1/
> >>>>
> >> <
> http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/a
> >> pache/maven/apache-maven/2.0.10-RC1/
> >>>>>
> >>>>
> >>>> The issues resolved for this release (so far) are here:
> >>>>
> >>>>
> >>>>
> >>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleNa
> >> me=Html&version=14112
> >>>>
> >>>> If you look at the Road Map view in JIRA, you'll notice that
> >>>> MNG-3639 is
> >>>> still open. This is because one of the possible solutions to this
> >>>> issue -
> >>>> and the only one that the Maven project really has control over -
> >>>> depends on
> >>>> re-releasing a new version of commons-build-plugin that will depend
> >>>> on the
> >>>> eventual 2.0.10 version of maven-script-ant.
> >>>>
> >>>> Please, try out this release candidate and let me know what's
> >>>> broken! Once
> >>>> things stabilize, I'll kick it out to the users to have a go, then
> >>>> if it's
> >>>> still stable after that (or, whatever RC we find is stable at that
> >>>> point),
> >>>> I'll call a vote to release. At that point, I'll run a new build to
> >>>> generate
> >>>> artifacts without the RC# suffix in the version.
> >>>>
> >>>> Thanks!
> >>>>
> >>>> -john
> >>>>
> >>>> --
> >>>> John Casey
> >>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> >>>> Blog: http://www.ejlife.net/blogs/buildchimp/
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>
> >>>>
> >>
> >> Thanks,
> >>
> >> Jason
> >>
> >> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder, Apache Maven
> >> jason at sonatype dot com
> >> ----------------------------------------------------------
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> 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
> >>
> >
> > Thanks,
> >
> > Jason
> >
> > ----------------------------------------------------------
> > Jason van Zyl
> > Founder, Apache Maven
> > jason at sonatype dot com
> > ----------------------------------------------------------
> >
> > We all have problems. How we deal with them is a measure of our worth.
> >
> > -- Unknown
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
>
> --
> Samuel Le Berrigaud
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [PLEASE TEST] Maven 2.0.10-RC1
Posted by Samuel Le Berrigaud <sa...@gmail.com>.
Hi all,
if you want to have both you surely could.
Why not adding the 2.0.10 RC1 version to Jira and any issue that is
found in the RC1 would have its affected version field set to 2.0.10
RC1 and the fix for to 2.0.10. That you get the nice release notes and
the metrics of what was found in the RC.
What do you think?
SaM
On Thu, Jul 17, 2008 at 12:40 AM, Jason van Zyl <ja...@maven.org> wrote:
> Fair enough, I was just trying to get some metrics around what surfaces
> after we call the RC, but we could probably do that if we noted the date as
> a filter.
>
> On 16-Jul-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:jason@maven.org]
>> 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 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 wrote:
>>
>>> Running mvn eclipse:eclipse on my project dump many stacktrace on the
>>> console :
>>>
>>> Downloading:
>>> http://sai1rennes:8888/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
>>> .apache
>>> .maven
>>> .wagon
>>> .providers
>>> .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:
>>> 132)
>>> ...
>>>
>>>
>>> The requested artifact is not present in the repo, but this is not
>>> blocker
>>> and maven 2.0.9 does not dump such errors.
>>>
>>>
>>>
>>> 2008/7/16 John Casey <jd...@commonjava.org>:
>>>
>>>> Hi again,
>>>>
>>>> As promised, I've staged the first release candidate for Maven
>>>> 2.0.10 here:
>>>>
>>>>
>>>>
>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apac
>> he/maven/apache-maven/2.0.10-RC1/
>>>>
>> <http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/a
>> pache/maven/apache-maven/2.0.10-RC1/
>>>>>
>>>>
>>>> The issues resolved for this release (so far) are here:
>>>>
>>>>
>>>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleNa
>> me=Html&version=14112
>>>>
>>>> If you look at the Road Map view in JIRA, you'll notice that
>>>> MNG-3639 is
>>>> still open. This is because one of the possible solutions to this
>>>> issue -
>>>> and the only one that the Maven project really has control over -
>>>> depends on
>>>> re-releasing a new version of commons-build-plugin that will depend
>>>> on the
>>>> eventual 2.0.10 version of maven-script-ant.
>>>>
>>>> Please, try out this release candidate and let me know what's
>>>> broken! Once
>>>> things stabilize, I'll kick it out to the users to have a go, then
>>>> if it's
>>>> still stable after that (or, whatever RC we find is stable at that
>>>> point),
>>>> I'll call a vote to release. At that point, I'll run a new build to
>>>> generate
>>>> artifacts without the RC# suffix in the version.
>>>>
>>>> Thanks!
>>>>
>>>> -john
>>>>
>>>> --
>>>> John Casey
>>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> jason at sonatype dot com
>> ----------------------------------------------------------
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
> We all have problems. How we deal with them is a measure of our worth.
>
> -- Unknown
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Samuel Le Berrigaud
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC1
Posted by Jason van Zyl <ja...@maven.org>.
Fair enough, I was just trying to get some metrics around what
surfaces after we call the RC, but we could probably do that if we
noted the date as a filter.
On 16-Jul-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:jason@maven.org]
> 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 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 wrote:
>
>> Running mvn eclipse:eclipse on my project dump many stacktrace on the
>> console :
>>
>> Downloading:
>> http://sai1rennes:8888/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
>> .apache
>> .maven
>> .wagon
>> .providers
>> .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:
>> 132)
>> ...
>>
>>
>> The requested artifact is not present in the repo, but this is not
>> blocker
>> and maven 2.0.9 does not dump such errors.
>>
>>
>>
>> 2008/7/16 John Casey <jd...@commonjava.org>:
>>
>>> Hi again,
>>>
>>> As promised, I've staged the first release candidate for Maven
>>> 2.0.10 here:
>>>
>>>
>>>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apac
> he/maven/apache-maven/2.0.10-RC1/
>>>
> <http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/a
> pache/maven/apache-maven/2.0.10-RC1/
>>>>
>>>
>>> The issues resolved for this release (so far) are here:
>>>
>>>
>>>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleNa
> me=Html&version=14112
>>>
>>> If you look at the Road Map view in JIRA, you'll notice that
>>> MNG-3639 is
>>> still open. This is because one of the possible solutions to this
>>> issue -
>>> and the only one that the Maven project really has control over -
>>> depends on
>>> re-releasing a new version of commons-build-plugin that will depend
>>> on the
>>> eventual 2.0.10 version of maven-script-ant.
>>>
>>> Please, try out this release candidate and let me know what's
>>> broken! Once
>>> things stabilize, I'll kick it out to the users to have a go, then
>>> if it's
>>> still stable after that (or, whatever RC we find is stable at that
>>> point),
>>> I'll call a vote to release. At that point, I'll run a new build to
>>> generate
>>> artifacts without the RC# suffix in the version.
>>>
>>> Thanks!
>>>
>>> -john
>>>
>>> --
>>> John Casey
>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> 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
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
We all have problems. How we deal with them is a measure of our worth.
-- Unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [PLEASE TEST] Maven 2.0.10-RC1
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
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:jason@maven.org]
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 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 wrote:
> Running mvn eclipse:eclipse on my project dump many stacktrace on the
> console :
>
> Downloading:
> http://sai1rennes:8888/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
> .apache
> .maven
> .wagon
> .providers
> .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:
> 132)
> ...
>
>
> The requested artifact is not present in the repo, but this is not
> blocker
> and maven 2.0.9 does not dump such errors.
>
>
>
> 2008/7/16 John Casey <jd...@commonjava.org>:
>
>> Hi again,
>>
>> As promised, I've staged the first release candidate for Maven
>> 2.0.10 here:
>>
>>
>>
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apac
he/maven/apache-maven/2.0.10-RC1/
>>
<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/a
pache/maven/apache-maven/2.0.10-RC1/
>> >
>>
>> The issues resolved for this release (so far) are here:
>>
>>
>>
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleNa
me=Html&version=14112
>>
>> If you look at the Road Map view in JIRA, you'll notice that
>> MNG-3639 is
>> still open. This is because one of the possible solutions to this
>> issue -
>> and the only one that the Maven project really has control over -
>> depends on
>> re-releasing a new version of commons-build-plugin that will depend
>> on the
>> eventual 2.0.10 version of maven-script-ant.
>>
>> Please, try out this release candidate and let me know what's
>> broken! Once
>> things stabilize, I'll kick it out to the users to have a go, then
>> if it's
>> still stable after that (or, whatever RC we find is stable at that
>> point),
>> I'll call a vote to release. At that point, I'll run a new build to
>> generate
>> artifacts without the RC# suffix in the version.
>>
>> Thanks!
>>
>> -john
>>
>> --
>> John Casey
>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
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.0.10-RC1
Posted by John Casey <jd...@commonjava.org>.
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.
>
> On 16-Jul-08, at 8:12 AM, nicolas de loof wrote:
>
>> Running mvn eclipse:eclipse on my project dump many stacktrace on the
>> console :
>>
>> Downloading:
>> http://sai1rennes:8888/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.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:132)
>>
>> ...
>>
>>
>> The requested artifact is not present in the repo, but this is not
>> blocker
>> and maven 2.0.9 does not dump such errors.
>>
>>
>>
>> 2008/7/16 John Casey <jd...@commonjava.org>:
>>
>>> Hi again,
>>>
>>> As promised, I've staged the first release candidate for Maven 2.0.10
>>> here:
>>>
>>>
>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/>
>>>
>>>
>>> The issues resolved for this release (so far) are here:
>>>
>>>
>>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112
>>>
>>>
>>> If you look at the Road Map view in JIRA, you'll notice that MNG-3639 is
>>> still open. This is because one of the possible solutions to this
>>> issue -
>>> and the only one that the Maven project really has control over -
>>> depends on
>>> re-releasing a new version of commons-build-plugin that will depend
>>> on the
>>> eventual 2.0.10 version of maven-script-ant.
>>>
>>> Please, try out this release candidate and let me know what's broken!
>>> Once
>>> things stabilize, I'll kick it out to the users to have a go, then if
>>> it's
>>> still stable after that (or, whatever RC we find is stable at that
>>> point),
>>> I'll call a vote to release. At that point, I'll run a new build to
>>> generate
>>> artifacts without the RC# suffix in the version.
>>>
>>> Thanks!
>>>
>>> -john
>>>
>>> --
>>> John Casey
>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC1
Posted by John Casey <jd...@commonjava.org>.
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 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 wrote:
>
>> Running mvn eclipse:eclipse on my project dump many stacktrace on the
>> console :
>>
>> Downloading:
>> http://sai1rennes:8888/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.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:132)
>>
>> ...
>>
>>
>> The requested artifact is not present in the repo, but this is not
>> blocker
>> and maven 2.0.9 does not dump such errors.
>>
>>
>>
>> 2008/7/16 John Casey <jd...@commonjava.org>:
>>
>>> Hi again,
>>>
>>> As promised, I've staged the first release candidate for Maven 2.0.10
>>> here:
>>>
>>>
>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/>
>>>
>>>
>>> The issues resolved for this release (so far) are here:
>>>
>>>
>>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112
>>>
>>>
>>> If you look at the Road Map view in JIRA, you'll notice that MNG-3639 is
>>> still open. This is because one of the possible solutions to this
>>> issue -
>>> and the only one that the Maven project really has control over -
>>> depends on
>>> re-releasing a new version of commons-build-plugin that will depend
>>> on the
>>> eventual 2.0.10 version of maven-script-ant.
>>>
>>> Please, try out this release candidate and let me know what's broken!
>>> Once
>>> things stabilize, I'll kick it out to the users to have a go, then if
>>> it's
>>> still stable after that (or, whatever RC we find is stable at that
>>> point),
>>> I'll call a vote to release. At that point, I'll run a new build to
>>> generate
>>> artifacts without the RC# suffix in the version.
>>>
>>> Thanks!
>>>
>>> -john
>>>
>>> --
>>> John Casey
>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC1
Posted by Jason van Zyl <ja...@maven.org>.
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 wrote:
> Running mvn eclipse:eclipse on my project dump many stacktrace on the
> console :
>
> Downloading:
> http://sai1rennes:8888/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
> .apache
> .maven
> .wagon
> .providers
> .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:
> 132)
> ...
>
>
> The requested artifact is not present in the repo, but this is not
> blocker
> and maven 2.0.9 does not dump such errors.
>
>
>
> 2008/7/16 John Casey <jd...@commonjava.org>:
>
>> Hi again,
>>
>> As promised, I've staged the first release candidate for Maven
>> 2.0.10 here:
>>
>>
>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/
>> <http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/
>> >
>>
>> The issues resolved for this release (so far) are here:
>>
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112
>>
>> If you look at the Road Map view in JIRA, you'll notice that
>> MNG-3639 is
>> still open. This is because one of the possible solutions to this
>> issue -
>> and the only one that the Maven project really has control over -
>> depends on
>> re-releasing a new version of commons-build-plugin that will depend
>> on the
>> eventual 2.0.10 version of maven-script-ant.
>>
>> Please, try out this release candidate and let me know what's
>> broken! Once
>> things stabilize, I'll kick it out to the users to have a go, then
>> if it's
>> still stable after that (or, whatever RC we find is stable at that
>> point),
>> I'll call a vote to release. At that point, I'll run a new build to
>> generate
>> artifacts without the RC# suffix in the version.
>>
>> Thanks!
>>
>> -john
>>
>> --
>> John Casey
>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC1
Posted by Brett Porter <br...@apache.org>.
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
expected behaviour so I'll file that in Wagon.
However, the printStackTrace() in the download monitor in maven-core
is probably erroneous - all those exceptions are still thrown by Wagon
and *should* be handled/logged by Maven if appropriate. I think that
line could go.
Cheers,
Brett
On 17/07/2008, at 12:15 AM, John Casey wrote:
> 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:8888/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
>> .apache
>> .maven
>> .wagon
>> .providers
>> .http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:
>> 132)
>> ...
>> The requested artifact is not present in the repo, but this is not
>> blocker
>> and maven 2.0.9 does not dump such errors.
>> 2008/7/16 John Casey <jd...@commonjava.org>:
>>> Hi again,
>>>
>>> As promised, I've staged the first release candidate for Maven
>>> 2.0.10 here:
>>>
>>>
>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/
>>> <http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/
>>> >
>>>
>>> The issues resolved for this release (so far) are here:
>>>
>>>
>>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112
>>>
>>> If you look at the Road Map view in JIRA, you'll notice that
>>> MNG-3639 is
>>> still open. This is because one of the possible solutions to this
>>> issue -
>>> and the only one that the Maven project really has control over -
>>> depends on
>>> re-releasing a new version of commons-build-plugin that will
>>> depend on the
>>> eventual 2.0.10 version of maven-script-ant.
>>>
>>> Please, try out this release candidate and let me know what's
>>> broken! Once
>>> things stabilize, I'll kick it out to the users to have a go, then
>>> if it's
>>> still stable after that (or, whatever RC we find is stable at that
>>> point),
>>> I'll call a vote to release. At that point, I'll run a new build
>>> to generate
>>> artifacts without the RC# suffix in the version.
>>>
>>> Thanks!
>>>
>>> -john
>>>
>>> --
>>> John Casey
>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
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.0.10-RC1
Posted by John Casey <jd...@commonjava.org>.
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:8888/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.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:132)
> ...
>
>
> The requested artifact is not present in the repo, but this is not blocker
> and maven 2.0.9 does not dump such errors.
>
>
>
> 2008/7/16 John Casey <jd...@commonjava.org>:
>
>> Hi again,
>>
>> As promised, I've staged the first release candidate for Maven 2.0.10 here:
>>
>>
>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/>
>>
>> The issues resolved for this release (so far) are here:
>>
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112
>>
>> If you look at the Road Map view in JIRA, you'll notice that MNG-3639 is
>> still open. This is because one of the possible solutions to this issue -
>> and the only one that the Maven project really has control over - depends on
>> re-releasing a new version of commons-build-plugin that will depend on the
>> eventual 2.0.10 version of maven-script-ant.
>>
>> Please, try out this release candidate and let me know what's broken! Once
>> things stabilize, I'll kick it out to the users to have a go, then if it's
>> still stable after that (or, whatever RC we find is stable at that point),
>> I'll call a vote to release. At that point, I'll run a new build to generate
>> artifacts without the RC# suffix in the version.
>>
>> Thanks!
>>
>> -john
>>
>> --
>> John Casey
>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC1
Posted by nicolas de loof <ni...@apache.org>.
Running mvn eclipse:eclipse on my project dump many stacktrace on the
console :
Downloading:
http://sai1rennes:8888/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.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:132)
...
The requested artifact is not present in the repo, but this is not blocker
and maven 2.0.9 does not dump such errors.
2008/7/16 John Casey <jd...@commonjava.org>:
> Hi again,
>
> As promised, I've staged the first release candidate for Maven 2.0.10 here:
>
>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/>
>
> The issues resolved for this release (so far) are here:
>
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112
>
> If you look at the Road Map view in JIRA, you'll notice that MNG-3639 is
> still open. This is because one of the possible solutions to this issue -
> and the only one that the Maven project really has control over - depends on
> re-releasing a new version of commons-build-plugin that will depend on the
> eventual 2.0.10 version of maven-script-ant.
>
> Please, try out this release candidate and let me know what's broken! Once
> things stabilize, I'll kick it out to the users to have a go, then if it's
> still stable after that (or, whatever RC we find is stable at that point),
> I'll call a vote to release. At that point, I'll run a new build to generate
> artifacts without the RC# suffix in the version.
>
> Thanks!
>
> -john
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [PLEASE TEST] Maven 2.0.10-RC1
Posted by John Casey <jd...@commonjava.org>.
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 <jd...@commonjava.org> 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 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.apache.ws.commons:XmlSchema
>>> The version 1.1 is set in the dependencyManagement of the parent.
>>>
>>> I have a testcase if you want.
>>>
>>> Should I open an issue or someone else already saw it ?
>>>
>>>
>>> On Wed, Jul 16, 2008 at 2:01 AM, John Casey <jd...@commonjava.org>
>>> wrote:
>>>
>>> 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
>>>> used in 2.0.9, with no problems).
>>>>
>>>> I rolled this plugin version back from 1.2-SNAPSHOT, so I assume that 1.1
>>>> contains a regression? I guess I should've done the leg work to make sure
>>>> the behavior I needed hadn't changed...
>>>>
>>>> I'll let everyone know as soon as I have an RC2 ready. The most notable
>>>> place this error is going to strike is when installing a POM-packaging
>>>> project that has a site descriptor in its src/site directory...
>>>>
>>>> -john
>>>>
>>>>
>>>> John Casey wrote:
>>>>
>>>> Hi again,
>>>>> As promised, I've staged the first release candidate for Maven 2.0.10
>>>>> here:
>>>>>
>>>>>
>>>>>
>>>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/>
>>>>> <
>>>>> http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/
>>>>> The issues resolved for this release (so far) are here:
>>>>>
>>>>>
>>>>>
>>>>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112
>>>>>
>>>>> If you look at the Road Map view in JIRA, you'll notice that MNG-3639 is
>>>>> still open. This is because one of the possible solutions to this issue
>>>>> -
>>>>> and the only one that the Maven project really has control over -
>>>>> depends on
>>>>> re-releasing a new version of commons-build-plugin that will depend on
>>>>> the
>>>>> eventual 2.0.10 version of maven-script-ant.
>>>>>
>>>>> Please, try out this release candidate and let me know what's broken!
>>>>> Once
>>>>> things stabilize, I'll kick it out to the users to have a go, then if
>>>>> it's
>>>>> still stable after that (or, whatever RC we find is stable at that
>>>>> point),
>>>>> I'll call a vote to release. At that point, I'll run a new build to
>>>>> generate
>>>>> artifacts without the RC# suffix in the version.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> -john
>>>>>
>>>>>
>>>>> --
>>>> John Casey
>>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>>
>> --
>> John Casey
>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC1
Posted by Arnaud HERITIER <ah...@gmail.com>.
Done.
http://jira.codehaus.org/browse/MNG-3667
cheers,
arnaud
On Wed, Jul 16, 2008 at 4:16 PM, John Casey <jd...@commonjava.org> 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 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.apache.ws.commons:XmlSchema
>> The version 1.1 is set in the dependencyManagement of the parent.
>>
>> I have a testcase if you want.
>>
>> Should I open an issue or someone else already saw it ?
>>
>>
>> On Wed, Jul 16, 2008 at 2:01 AM, John Casey <jd...@commonjava.org>
>> wrote:
>>
>> 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
>>> used in 2.0.9, with no problems).
>>>
>>> I rolled this plugin version back from 1.2-SNAPSHOT, so I assume that 1.1
>>> contains a regression? I guess I should've done the leg work to make sure
>>> the behavior I needed hadn't changed...
>>>
>>> I'll let everyone know as soon as I have an RC2 ready. The most notable
>>> place this error is going to strike is when installing a POM-packaging
>>> project that has a site descriptor in its src/site directory...
>>>
>>> -john
>>>
>>>
>>> John Casey wrote:
>>>
>>> Hi again,
>>>>
>>>> As promised, I've staged the first release candidate for Maven 2.0.10
>>>> here:
>>>>
>>>>
>>>>
>>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/>
>>>> <
>>>> http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/
>>>> >
>>>>
>>>> The issues resolved for this release (so far) are here:
>>>>
>>>>
>>>>
>>>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112
>>>>
>>>> If you look at the Road Map view in JIRA, you'll notice that MNG-3639 is
>>>> still open. This is because one of the possible solutions to this issue
>>>> -
>>>> and the only one that the Maven project really has control over -
>>>> depends on
>>>> re-releasing a new version of commons-build-plugin that will depend on
>>>> the
>>>> eventual 2.0.10 version of maven-script-ant.
>>>>
>>>> Please, try out this release candidate and let me know what's broken!
>>>> Once
>>>> things stabilize, I'll kick it out to the users to have a go, then if
>>>> it's
>>>> still stable after that (or, whatever RC we find is stable at that
>>>> point),
>>>> I'll call a vote to release. At that point, I'll run a new build to
>>>> generate
>>>> artifacts without the RC# suffix in the version.
>>>>
>>>> Thanks!
>>>>
>>>> -john
>>>>
>>>>
>>>> --
>>> John Casey
>>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>>
>>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [PLEASE TEST] Maven 2.0.10-RC1
Posted by John Casey <jd...@commonjava.org>.
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 project with a dependency to
> org.codehaus.xfire:xfire-core:1.2.6
> In the xfire-core pom we have a dependency to
> org.apache.ws.commons:XmlSchema
> The version 1.1 is set in the dependencyManagement of the parent.
>
> I have a testcase if you want.
>
> Should I open an issue or someone else already saw it ?
>
>
> On Wed, Jul 16, 2008 at 2:01 AM, John Casey <jd...@commonjava.org> wrote:
>
>> 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
>> used in 2.0.9, with no problems).
>>
>> I rolled this plugin version back from 1.2-SNAPSHOT, so I assume that 1.1
>> contains a regression? I guess I should've done the leg work to make sure
>> the behavior I needed hadn't changed...
>>
>> I'll let everyone know as soon as I have an RC2 ready. The most notable
>> place this error is going to strike is when installing a POM-packaging
>> project that has a site descriptor in its src/site directory...
>>
>> -john
>>
>>
>> John Casey wrote:
>>
>>> Hi again,
>>>
>>> As promised, I've staged the first release candidate for Maven 2.0.10
>>> here:
>>>
>>>
>>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/>
>>>
>>> The issues resolved for this release (so far) are here:
>>>
>>>
>>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112
>>>
>>> If you look at the Road Map view in JIRA, you'll notice that MNG-3639 is
>>> still open. This is because one of the possible solutions to this issue -
>>> and the only one that the Maven project really has control over - depends on
>>> re-releasing a new version of commons-build-plugin that will depend on the
>>> eventual 2.0.10 version of maven-script-ant.
>>>
>>> Please, try out this release candidate and let me know what's broken! Once
>>> things stabilize, I'll kick it out to the users to have a go, then if it's
>>> still stable after that (or, whatever RC we find is stable at that point),
>>> I'll call a vote to release. At that point, I'll run a new build to generate
>>> artifacts without the RC# suffix in the version.
>>>
>>> Thanks!
>>>
>>> -john
>>>
>>>
>> --
>> John Casey
>> Developer, PMC Member - Apache Maven (http://maven.apache.org)
>> Blog: http://www.ejlife.net/blogs/buildchimp/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC1
Posted by Arnaud HERITIER <ah...@gmail.com>.
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.apache.ws.commons:XmlSchema
The version 1.1 is set in the dependencyManagement of the parent.
I have a testcase if you want.
Should I open an issue or someone else already saw it ?
On Wed, Jul 16, 2008 at 2:01 AM, John Casey <jd...@commonjava.org> wrote:
> 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
> used in 2.0.9, with no problems).
>
> I rolled this plugin version back from 1.2-SNAPSHOT, so I assume that 1.1
> contains a regression? I guess I should've done the leg work to make sure
> the behavior I needed hadn't changed...
>
> I'll let everyone know as soon as I have an RC2 ready. The most notable
> place this error is going to strike is when installing a POM-packaging
> project that has a site descriptor in its src/site directory...
>
> -john
>
>
> John Casey wrote:
>
>> Hi again,
>>
>> As promised, I've staged the first release candidate for Maven 2.0.10
>> here:
>>
>>
>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/<http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/>
>>
>> The issues resolved for this release (so far) are here:
>>
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112
>>
>> If you look at the Road Map view in JIRA, you'll notice that MNG-3639 is
>> still open. This is because one of the possible solutions to this issue -
>> and the only one that the Maven project really has control over - depends on
>> re-releasing a new version of commons-build-plugin that will depend on the
>> eventual 2.0.10 version of maven-script-ant.
>>
>> Please, try out this release candidate and let me know what's broken! Once
>> things stabilize, I'll kick it out to the users to have a go, then if it's
>> still stable after that (or, whatever RC we find is stable at that point),
>> I'll call a vote to release. At that point, I'll run a new build to generate
>> artifacts without the RC# suffix in the version.
>>
>> Thanks!
>>
>> -john
>>
>>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [PLEASE TEST] Maven 2.0.10-RC1
Posted by John Casey <jd...@commonjava.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 used in 2.0.9, with no problems).
I rolled this plugin version back from 1.2-SNAPSHOT, so I assume that
1.1 contains a regression? I guess I should've done the leg work to make
sure the behavior I needed hadn't changed...
I'll let everyone know as soon as I have an RC2 ready. The most notable
place this error is going to strike is when installing a POM-packaging
project that has a site descriptor in its src/site directory...
-john
John Casey wrote:
> Hi again,
>
> As promised, I've staged the first release candidate for Maven 2.0.10 here:
>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/
>
>
> The issues resolved for this release (so far) are here:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112
>
>
> If you look at the Road Map view in JIRA, you'll notice that MNG-3639 is
> still open. This is because one of the possible solutions to this issue
> - and the only one that the Maven project really has control over -
> depends on re-releasing a new version of commons-build-plugin that will
> depend on the eventual 2.0.10 version of maven-script-ant.
>
> Please, try out this release candidate and let me know what's broken!
> Once things stabilize, I'll kick it out to the users to have a go, then
> if it's still stable after that (or, whatever RC we find is stable at
> that point), I'll call a vote to release. At that point, I'll run a new
> build to generate artifacts without the RC# suffix in the version.
>
> Thanks!
>
> -john
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC1
Posted by John Casey <jd...@commonjava.org>.
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?
>
> Cheers,
>
> Henrique
>
> hprange:pas-human-resources-model hprange$ mvn clean install
> [INFO] Scanning for projects...
> [...]
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] null
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.artifact.resolver.ResolutionNode.getKey(ResolutionNode.java:84)
>
> at
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:393)
>
> at
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:424)
>
> at
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:424)
>
> at
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:424)
>
> at
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74)
>
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300)
>
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288)
>
> at
> org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1451)
>
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:406)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:578)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:519)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:498)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:350)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:311)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:162)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:127)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>
>
> John Casey wrote:
>> Hi again,
>>
>> As promised, I've staged the first release candidate for Maven 2.0.10
>> here:
>>
>> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/
>>
>>
>> The issues resolved for this release (so far) are here:
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112
>>
>>
>> If you look at the Road Map view in JIRA, you'll notice that MNG-3639
>> is still open. This is because one of the possible solutions to this
>> issue - and the only one that the Maven project really has control
>> over - depends on re-releasing a new version of commons-build-plugin
>> that will depend on the eventual 2.0.10 version of maven-script-ant.
>>
>> Please, try out this release candidate and let me know what's broken!
>> Once things stabilize, I'll kick it out to the users to have a go,
>> then if it's still stable after that (or, whatever RC we find is
>> stable at that point), I'll call a vote to release. At that point,
>> I'll run a new build to generate artifacts without the RC# suffix in
>> the version.
>>
>> Thanks!
>>
>> -john
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC1
Posted by Henrique Prange <hp...@gmail.com>.
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 clean install
[INFO] Scanning for projects...
[...]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] null
[INFO]
------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.artifact.resolver.ResolutionNode.getKey(ResolutionNode.java:84)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:393)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:424)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:424)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:424)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288)
at
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1451)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:406)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:578)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:519)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:498)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:350)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:162)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:127)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
John Casey wrote:
> Hi again,
>
> As promised, I've staged the first release candidate for Maven 2.0.10 here:
>
> http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC1/org/apache/maven/apache-maven/2.0.10-RC1/
>
>
> The issues resolved for this release (so far) are here:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14112
>
>
> If you look at the Road Map view in JIRA, you'll notice that MNG-3639 is
> still open. This is because one of the possible solutions to this issue
> - and the only one that the Maven project really has control over -
> depends on re-releasing a new version of commons-build-plugin that will
> depend on the eventual 2.0.10 version of maven-script-ant.
>
> Please, try out this release candidate and let me know what's broken!
> Once things stabilize, I'll kick it out to the users to have a go, then
> if it's still stable after that (or, whatever RC we find is stable at
> that point), I'll call a vote to release. At that point, I'll run a new
> build to generate artifacts without the RC# suffix in the version.
>
> Thanks!
>
> -john
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org