You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by John Casey <jd...@commonjava.org> on 2008/09/10 05:32:31 UTC

[PLEASE TEST] Maven 2.1.0-M1-RC17

Hi,

I've fixed MNG-3748, where illegal elements in the settings.xml were not 
triggering build failure. Anyway, this release candidate includes a fix 
for that issue:

http://people.apache.org/~jdcasey/stage/current-maven-RC/

Enjoy, and let me know if you have problems.

Thanks,

-john

---
John Casey
Developer and PMC Member, Apache Maven (http://maven.apache.org)
Member, Apache Software Foundation
Blog: http://www.ejlife.net/blogs/buildchimp

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Maven concurrent builds Was: RE: [PLEASE TEST] Maven 2.1.0-M1-RC17

Posted by Chris Schmidt <cs...@prospricing.com>.
  Thanks for the information.  I'll keep tabs on the feature.  In the
meantime, using the local repository command may be the answer I need to
build under the same user account for multiple concurrent builds.

Thanks,

  Chris

-----Original Message-----
From: Brett Porter [mailto:brett.porter@gmail.com] 
Sent: Wednesday, September 10, 2008 7:50 AM
To: Maven Users List
Subject: Re: [PLEASE TEST] Maven 2.1.0-M1-RC17

This has been brought up on the development list.
We've adjusted the release plans for 2.1 to reduce the timelines for
that
and subsequent releases (this release is based on the former 2.0.10
release,
with some additional features). Given the demand this is one of the
higher
priority features. The issue to vote/watch is MNG-2802.

Cheers,
Brett

2008/9/10 Chris Schmidt <cs...@prospricing.com>

>  Earlier in the year, there was a question about concurrent access to
a
> local repository on a server.  It was mentioned that an issue in
maven2
> could cause race conditions when multiple processes update the same
> local repository, but that it would be fixed in 2.1.  I looked at the
> list of defects in jira, but didn't see anything specifically
mentioning
> this issue.  Do you know if this issue has been resolved in the 2.1
> release candidate?
>
> Thanks,
>
>  Chris Schmidt
>
> -----Original Message-----
> From: John Casey [mailto:jdcasey@commonjava.org]
> Sent: Tuesday, September 09, 2008 10:33 PM
> To: Maven Developers List; Maven Users List
> Subject: [PLEASE TEST] Maven 2.1.0-M1-RC17
>
> Hi,
>
> I've fixed MNG-3748, where illegal elements in the settings.xml were
not
>
> triggering build failure. Anyway, this release candidate includes a
fix
> for that issue:
>
> http://people.apache.org/~jdcasey/stage/current-maven-RC/
>
> Enjoy, and let me know if you have problems.
>
> Thanks,
>
> -john
>
> ---
> John Casey
> Developer and PMC Member, Apache Maven (http://maven.apache.org)
> Member, Apache Software Foundation
> Blog: http://www.ejlife.net/blogs/buildchimp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [PLEASE TEST] Maven 2.1.0-M1-RC17

Posted by Brett Porter <br...@gmail.com>.
This has been brought up on the development list.
We've adjusted the release plans for 2.1 to reduce the timelines for that
and subsequent releases (this release is based on the former 2.0.10 release,
with some additional features). Given the demand this is one of the higher
priority features. The issue to vote/watch is MNG-2802.

Cheers,
Brett

2008/9/10 Chris Schmidt <cs...@prospricing.com>

>  Earlier in the year, there was a question about concurrent access to a
> local repository on a server.  It was mentioned that an issue in maven2
> could cause race conditions when multiple processes update the same
> local repository, but that it would be fixed in 2.1.  I looked at the
> list of defects in jira, but didn't see anything specifically mentioning
> this issue.  Do you know if this issue has been resolved in the 2.1
> release candidate?
>
> Thanks,
>
>  Chris Schmidt
>
> -----Original Message-----
> From: John Casey [mailto:jdcasey@commonjava.org]
> Sent: Tuesday, September 09, 2008 10:33 PM
> To: Maven Developers List; Maven Users List
> Subject: [PLEASE TEST] Maven 2.1.0-M1-RC17
>
> Hi,
>
> I've fixed MNG-3748, where illegal elements in the settings.xml were not
>
> triggering build failure. Anyway, this release candidate includes a fix
> for that issue:
>
> http://people.apache.org/~jdcasey/stage/current-maven-RC/
>
> Enjoy, and let me know if you have problems.
>
> Thanks,
>
> -john
>
> ---
> John Casey
> Developer and PMC Member, Apache Maven (http://maven.apache.org)
> Member, Apache Software Foundation
> Blog: http://www.ejlife.net/blogs/buildchimp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

RE: [PLEASE TEST] Maven 2.1.0-M1-RC17

Posted by Chris Schmidt <cs...@prospricing.com>.
  Earlier in the year, there was a question about concurrent access to a
local repository on a server.  It was mentioned that an issue in maven2
could cause race conditions when multiple processes update the same
local repository, but that it would be fixed in 2.1.  I looked at the
list of defects in jira, but didn't see anything specifically mentioning
this issue.  Do you know if this issue has been resolved in the 2.1
release candidate?  

Thanks,

  Chris Schmidt

-----Original Message-----
From: John Casey [mailto:jdcasey@commonjava.org] 
Sent: Tuesday, September 09, 2008 10:33 PM
To: Maven Developers List; Maven Users List
Subject: [PLEASE TEST] Maven 2.1.0-M1-RC17

Hi,

I've fixed MNG-3748, where illegal elements in the settings.xml were not

triggering build failure. Anyway, this release candidate includes a fix 
for that issue:

http://people.apache.org/~jdcasey/stage/current-maven-RC/

Enjoy, and let me know if you have problems.

Thanks,

-john

---
John Casey
Developer and PMC Member, Apache Maven (http://maven.apache.org)
Member, Apache Software Foundation
Blog: http://www.ejlife.net/blogs/buildchimp

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [PLEASE TEST] Maven 2.1.0-M1-RC17

Posted by Jorg Heymans <jo...@gmail.com>.
On Wed, Sep 10, 2008 at 5:32 AM, John Casey <jd...@commonjava.org> wrote:

> Hi,
>
> I've fixed MNG-3748, where illegal elements in the settings.xml were not
> triggering build failure. Anyway, this release candidate includes a fix for
> that issue:
>
> http://people.apache.org/~jdcasey/stage/current-maven-RC/<http://people.apache.org/%7Ejdcasey/stage/current-maven-RC/>



migrated our Hudson instance from RC-12 to RC-17, all still working fine !


Thanks,
Jorg

Re: [PLEASE TEST] Maven 2.1.0-M1-RC17

Posted by Fabrice Bellingard <be...@gmail.com>.
Still works fine for my builds :-)

- Fabrice
bellingard@apache.org


On Wed, Sep 10, 2008 at 5:32 AM, John Casey <jd...@commonjava.org> wrote:

> Hi,
>
> I've fixed MNG-3748, where illegal elements in the settings.xml were not
> triggering build failure. Anyway, this release candidate includes a fix for
> that issue:
>
> http://people.apache.org/~jdcasey/stage/current-maven-RC/<http://people.apache.org/%7Ejdcasey/stage/current-maven-RC/>
>
> Enjoy, and let me know if you have problems.
>
> Thanks,
>
> -john
>
> ---
> John Casey
> Developer and PMC Member, Apache Maven (http://maven.apache.org)
> Member, Apache Software Foundation
> 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.1.0-M1-RC17

Posted by Michael McCallum <gh...@apache.org>.
I've been testing RC17 as the external version for m2eclipse and its much much 
better than 2.0.9 or any of the other RC's. Its actually snappy.

had some really weird things with plugin resolutions and stack overflows 
gioing on intermittently but they all look to be resolved.

good work.


-- 
Michael McCallum
Enterprise Engineer
mailto:gholam@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [PLEASE TEST] Maven 2.1.0-M1-RC17

Posted by John Casey <jd...@commonjava.org>.
Yeah, originalModel looks like it's saved off after inheritance occurs, 
so the only thing I was able to do this go around was to keep it from 
getting polluted by plugin information that's discovered by the plugin 
manager during build execution...so, if you don't have a plugin version 
legitimately from your POM or one of its parents, it won't ever appear 
in the originalModel.

Stephen Connolly wrote:
> BTW, I think we're still getting the
> project.getOriginalModel().getBuild().getPluginManagement() containing the
> super-pom (but as that is 2.0.9 behaviour it's not a "regression" form
> 2.0.9... perhaps from previous versions but not from 2.0.9)
> 
> On Thu, Sep 11, 2008 at 12:50 PM, Stephen Connolly <
> stephen.alan.connolly@gmail.com> wrote:
> 
>> Seems fine here too
>>
>>
>> On Thu, Sep 11, 2008 at 12:29 PM, Peter Horlock <
>> peter.horlock@googlemail.com> wrote:
>>
>>> RC17 runs smooth and nicely here too...
>>>
>>>
>>> Thanks,
>>>
>>> Peter
>>>
>>
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [PLEASE TEST] Maven 2.1.0-M1-RC17

Posted by Stephen Connolly <st...@gmail.com>.
BTW, I think we're still getting the
project.getOriginalModel().getBuild().getPluginManagement() containing the
super-pom (but as that is 2.0.9 behaviour it's not a "regression" form
2.0.9... perhaps from previous versions but not from 2.0.9)

On Thu, Sep 11, 2008 at 12:50 PM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:

> Seems fine here too
>
>
> On Thu, Sep 11, 2008 at 12:29 PM, Peter Horlock <
> peter.horlock@googlemail.com> wrote:
>
>> RC17 runs smooth and nicely here too...
>>
>>
>> Thanks,
>>
>> Peter
>>
>
>

Re: [PLEASE TEST] Maven 2.1.0-M1-RC17

Posted by Stephen Connolly <st...@gmail.com>.
Seems fine here too

On Thu, Sep 11, 2008 at 12:29 PM, Peter Horlock <
peter.horlock@googlemail.com> wrote:

> RC17 runs smooth and nicely here too...
>
>
> Thanks,
>
> Peter
>

Re: [PLEASE TEST] Maven 2.1.0-M1-RC17

Posted by Peter Horlock <pe...@googlemail.com>.
RC17 runs smooth and nicely here too...


Thanks,

Peter

Re: [PLEASE TEST] Maven 2.1.0-M1-RC17

Posted by Martin Höller <ma...@xss.co.at>.
On Wednesday 10 September 2008 John Casey wrote:
> http://people.apache.org/~jdcasey/stage/current-maven-RC/
>
> Enjoy, and let me know if you have problems.

No problems here with RC17.

thanks,
- martin