You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by John Casey <jd...@commonjava.org> on 2009/06/23 02:03:19 UTC
[PLEASE TEST] Maven 2.2.0-RC4 & Maven Wagon 1.0-beta-6
Hi everyone,
As I'm sure you're aware, I've tried twice now to get a clean vote done
for Maven 2.2.0. In each case, we've run into blocking bugs that have
caused me to retract the vote and fix the code.
Well, with the latest bug that Brian found, we're now dependent on some
configuration updates that are available on the trunk of Maven Wagon.
I've added configuration for the non-lightweight http wagon to address:
WAGON-270 - preemptive auth in non-lightweight http wagon causes
Unauthorized responses from some servers
WAGON-264 - compressed tarball download problems
WAGON-271 - Provide configurability of httpclient parameters to allow
user to tell Maven to ignore cookies
The top issue relates to Brian's problem, and the bottom issue relates
to MNG-4165, which is also in the release notes for Maven 2.2.0. The
middle issue was a side-effect of fixing the other two.
I'd like to have as many eyes on this release candidate as I can get.
I'm doing another RC instead of a new vote thread because I don't want
to push it too much and wind up with a profusion of different artifacts
in people's local repositories marked as being part of Maven 2.2.0 when
they are really part of failed votes for 2.2.0...
Once I'm confident this RC is good to go, I'll call votes for both Wagon
1.0-beta-6 and Maven 2.2.0.
You can find the staging repositories here:
Wagon:
https://repository.apache.org/content/repositories/maven-staging-002/
Maven 2.2.0-RC4:
https://repository.apache.org/content/repositories/maven-staging-006/
You can find release notes here:
Wagon:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335&styleName=Html&version=15403
Maven:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=15103
Please give these a try, and let me know what you find!
Thanks,
-john
---
John Casey
Developer and PMC Member, Apache Maven (http://maven.apache.org)
Member, Apache Software Foundation
"What we have to learn to do, we learn by doing."
-Aristotle
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.2.0-RC4 & Maven Wagon 1.0-beta-6
Posted by John Casey <jd...@commonjava.org>.
Okay, the correct staging repository URL for Maven 2.2.0-RC4 is:
https://repository.apache.org/content/repositories/maven-staging-007/
Remember, this version contains the staged version of Wagon 1.0-beta-6.
Thanks,
-john
John Casey wrote:
> Ugh, that Maven repository location is wrong. I'm re-staging this RC,
> and I'll post the staging repository once that's done. Sorry for the
> confusion.
>
> -john
>
> John Casey wrote:
>> Hi everyone,
>>
>> As I'm sure you're aware, I've tried twice now to get a clean vote
>> done for Maven 2.2.0. In each case, we've run into blocking bugs that
>> have caused me to retract the vote and fix the code.
>>
>> Well, with the latest bug that Brian found, we're now dependent on
>> some configuration updates that are available on the trunk of Maven
>> Wagon. I've added configuration for the non-lightweight http wagon to
>> address:
>>
>> WAGON-270 - preemptive auth in non-lightweight http wagon causes
>> Unauthorized responses from some servers
>>
>> WAGON-264 - compressed tarball download problems
>>
>> WAGON-271 - Provide configurability of httpclient parameters to allow
>> user to tell Maven to ignore cookies
>>
>> The top issue relates to Brian's problem, and the bottom issue relates
>> to MNG-4165, which is also in the release notes for Maven 2.2.0. The
>> middle issue was a side-effect of fixing the other two.
>>
>> I'd like to have as many eyes on this release candidate as I can get.
>> I'm doing another RC instead of a new vote thread because I don't want
>> to push it too much and wind up with a profusion of different
>> artifacts in people's local repositories marked as being part of Maven
>> 2.2.0 when they are really part of failed votes for 2.2.0...
>>
>> Once I'm confident this RC is good to go, I'll call votes for both
>> Wagon 1.0-beta-6 and Maven 2.2.0.
>>
>> You can find the staging repositories here:
>>
>> Wagon:
>>
>> https://repository.apache.org/content/repositories/maven-staging-002/
>>
>> Maven 2.2.0-RC4:
>>
>> https://repository.apache.org/content/repositories/maven-staging-006/
>>
>>
>> You can find release notes here:
>>
>> Wagon:
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335&styleName=Html&version=15403
>>
>>
>> Maven:
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=15103
>>
>>
>>
>> Please give these a try, and let me know what you find!
>>
>> Thanks,
>>
>> -john
>>
>> ---
>> John Casey
>> Developer and PMC Member, Apache Maven (http://maven.apache.org)
>> Member, Apache Software Foundation
>>
>> "What we have to learn to do, we learn by doing."
>> -Aristotle
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.2.0-RC4 & Maven Wagon 1.0-beta-6
Posted by John Casey <jd...@commonjava.org>.
Ugh, that Maven repository location is wrong. I'm re-staging this RC,
and I'll post the staging repository once that's done. Sorry for the
confusion.
-john
John Casey wrote:
> Hi everyone,
>
> As I'm sure you're aware, I've tried twice now to get a clean vote done
> for Maven 2.2.0. In each case, we've run into blocking bugs that have
> caused me to retract the vote and fix the code.
>
> Well, with the latest bug that Brian found, we're now dependent on some
> configuration updates that are available on the trunk of Maven Wagon.
> I've added configuration for the non-lightweight http wagon to address:
>
> WAGON-270 - preemptive auth in non-lightweight http wagon causes
> Unauthorized responses from some servers
>
> WAGON-264 - compressed tarball download problems
>
> WAGON-271 - Provide configurability of httpclient parameters to allow
> user to tell Maven to ignore cookies
>
> The top issue relates to Brian's problem, and the bottom issue relates
> to MNG-4165, which is also in the release notes for Maven 2.2.0. The
> middle issue was a side-effect of fixing the other two.
>
> I'd like to have as many eyes on this release candidate as I can get.
> I'm doing another RC instead of a new vote thread because I don't want
> to push it too much and wind up with a profusion of different artifacts
> in people's local repositories marked as being part of Maven 2.2.0 when
> they are really part of failed votes for 2.2.0...
>
> Once I'm confident this RC is good to go, I'll call votes for both Wagon
> 1.0-beta-6 and Maven 2.2.0.
>
> You can find the staging repositories here:
>
> Wagon:
>
> https://repository.apache.org/content/repositories/maven-staging-002/
>
> Maven 2.2.0-RC4:
>
> https://repository.apache.org/content/repositories/maven-staging-006/
>
>
> You can find release notes here:
>
> Wagon:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335&styleName=Html&version=15403
>
>
> Maven:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=15103
>
>
>
> Please give these a try, and let me know what you find!
>
> Thanks,
>
> -john
>
> ---
> John Casey
> Developer and PMC Member, Apache Maven (http://maven.apache.org)
> Member, Apache Software Foundation
>
> "What we have to learn to do, we learn by doing."
> -Aristotle
>
> ---------------------------------------------------------------------
> 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.2.0-RC4 & Maven Wagon 1.0-beta-6
Posted by Brian Fox <br...@infinity.nu>.
Nice. That's an old bug that I saw back in ~2.0.5 but it comes and
goes. This is some core plexus threading issue that isn't specific to
this release. Search jira for that message....
On Thu, Jun 25, 2009 at 12:52 AM, Jörg Schaible<jo...@gmx.de> wrote:
> Hi John,
>
> John Casey wrote at Dienstag, 23. Juni 2009 02:03:
>
>> Hi everyone,
>>
>> As I'm sure you're aware, I've tried twice now to get a clean vote done
>> for Maven 2.2.0. In each case, we've run into blocking bugs that have
>> caused me to retract the vote and fix the code.
>>
>> Well, with the latest bug that Brian found, we're now dependent on some
>> configuration updates that are available on the trunk of Maven Wagon.
>> I've added configuration for the non-lightweight http wagon to address:
>>
>> WAGON-270 - preemptive auth in non-lightweight http wagon causes
>> Unauthorized responses from some servers
>>
>> WAGON-264 - compressed tarball download problems
>>
>> WAGON-271 - Provide configurability of httpclient parameters to allow
>> user to tell Maven to ignore cookies
>>
>> The top issue relates to Brian's problem, and the bottom issue relates
>> to MNG-4165, which is also in the release notes for Maven 2.2.0. The
>> middle issue was a side-effect of fixing the other two.
>>
>> I'd like to have as many eyes on this release candidate as I can get.
>> I'm doing another RC instead of a new vote thread because I don't want
>> to push it too much and wind up with a profusion of different artifacts
>> in people's local repositories marked as being part of Maven 2.2.0 when
>> they are really part of failed votes for 2.2.0...
>>
>> Once I'm confident this RC is good to go, I'll call votes for both Wagon
>> 1.0-beta-6 and Maven 2.2.0.
>
> I've not tested releasing with the current version, but at least I can build
> my quite big projects with this release without problems. However, I have
> tons of those warnings for a lot of modules:
>
> ============= %< ==============
> [WARNING] Component returned which is not the same manager. Ignored.
> component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
> [WARNING] Component returned which is not the same manager. Ignored.
> component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
> [WARNING] Component returned which is not the same manager. Ignored.
> component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
> [WARNING] Component returned which is not the same manager. Ignored.
> component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
> [WARNING] Component returned which is not the same manager. Ignored.
> component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
> [WARNING] Component returned which is not the same manager. Ignored.
> component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
> [WARNING] Component returned which is not the same manager. Ignored.
> component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
> [WARNING] Component returned which is not the same manager. Ignored.
> component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
> ...
> ============= %< ==============
>
> - Jörg
>
>
>
> ---------------------------------------------------------------------
> 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.2.0-RC4 & Maven Wagon 1.0-beta-6
Posted by Jörg Schaible <jo...@gmx.de>.
Hi John,
John Casey wrote at Dienstag, 23. Juni 2009 02:03:
> Hi everyone,
>
> As I'm sure you're aware, I've tried twice now to get a clean vote done
> for Maven 2.2.0. In each case, we've run into blocking bugs that have
> caused me to retract the vote and fix the code.
>
> Well, with the latest bug that Brian found, we're now dependent on some
> configuration updates that are available on the trunk of Maven Wagon.
> I've added configuration for the non-lightweight http wagon to address:
>
> WAGON-270 - preemptive auth in non-lightweight http wagon causes
> Unauthorized responses from some servers
>
> WAGON-264 - compressed tarball download problems
>
> WAGON-271 - Provide configurability of httpclient parameters to allow
> user to tell Maven to ignore cookies
>
> The top issue relates to Brian's problem, and the bottom issue relates
> to MNG-4165, which is also in the release notes for Maven 2.2.0. The
> middle issue was a side-effect of fixing the other two.
>
> I'd like to have as many eyes on this release candidate as I can get.
> I'm doing another RC instead of a new vote thread because I don't want
> to push it too much and wind up with a profusion of different artifacts
> in people's local repositories marked as being part of Maven 2.2.0 when
> they are really part of failed votes for 2.2.0...
>
> Once I'm confident this RC is good to go, I'll call votes for both Wagon
> 1.0-beta-6 and Maven 2.2.0.
I've not tested releasing with the current version, but at least I can build
my quite big projects with this release without problems. However, I have
tons of those warnings for a lot of modules:
============= %< ==============
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.SystemPropertyProfileActivator@1aa57fb
...
============= %< ==============
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.2.0-RC4 & Maven Wagon 1.0-beta-6
Posted by Brian Fox <br...@infinity.nu>.
I say leave it out.
On Tue, Jun 23, 2009 at 10:26 AM, John Casey<jd...@commonjava.org> wrote:
> FWIW, the following URL at repository.apache.org includes the staging
> repository for wagon:
>
> https://repository.apache.org/content/groups/staging/
>
> I've added this repository location to the group used by the Hudson
> instance, and it's now building Maven 2.2.0-RC5-SNAPSHOT (the next version
> on the maven-2.2.0-RC branch) successfully.
>
> I'm not entirely sure how valuable it'd be to add the repository to the POM
> in this branch, since we'll just have to remove it for the vote...and since
> I was really hoping to vote for both projects at the same time. If this is a
> major issue, I'm sure we can find a way to work around it.
>
> -john
>
> Brett Porter wrote:
>>
>> I'll try and get some time to look through these, as I have some questions
>> from what I've seen at a glance.
>>
>> It looks like you need to temporarily add the Wagon staging repo to the
>> POM so that the hudson build will succeed though.
>>
>> - Brett
>>
>> On 23/06/2009, at 10:03 AM, John Casey wrote:
>>
>>> Hi everyone,
>>>
>>> As I'm sure you're aware, I've tried twice now to get a clean vote done
>>> for Maven 2.2.0. In each case, we've run into blocking bugs that have caused
>>> me to retract the vote and fix the code.
>>>
>>> Well, with the latest bug that Brian found, we're now dependent on some
>>> configuration updates that are available on the trunk of Maven Wagon. I've
>>> added configuration for the non-lightweight http wagon to address:
>>>
>>> WAGON-270 - preemptive auth in non-lightweight http wagon causes
>>> Unauthorized responses from some servers
>>>
>>> WAGON-264 - compressed tarball download problems
>>>
>>> WAGON-271 - Provide configurability of httpclient parameters to allow
>>> user to tell Maven to ignore cookies
>>>
>>> The top issue relates to Brian's problem, and the bottom issue relates to
>>> MNG-4165, which is also in the release notes for Maven 2.2.0. The middle
>>> issue was a side-effect of fixing the other two.
>>>
>>> I'd like to have as many eyes on this release candidate as I can get. I'm
>>> doing another RC instead of a new vote thread because I don't want to push
>>> it too much and wind up with a profusion of different artifacts in people's
>>> local repositories marked as being part of Maven 2.2.0 when they are really
>>> part of failed votes for 2.2.0...
>>>
>>> Once I'm confident this RC is good to go, I'll call votes for both Wagon
>>> 1.0-beta-6 and Maven 2.2.0.
>>>
>>> You can find the staging repositories here:
>>>
>>> Wagon:
>>>
>>> https://repository.apache.org/content/repositories/maven-staging-002/
>>>
>>> Maven 2.2.0-RC4:
>>>
>>> https://repository.apache.org/content/repositories/maven-staging-006/
>>>
>>>
>>> You can find release notes here:
>>>
>>> Wagon:
>>>
>>>
>>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335&styleName=Html&version=15403
>>>
>>> Maven:
>>>
>>>
>>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=15103
>>>
>>>
>>> Please give these a try, and let me know what you find!
>>>
>>> Thanks,
>>>
>>> -john
>>>
>>> ---
>>> John Casey
>>> Developer and PMC Member, Apache Maven (http://maven.apache.org)
>>> Member, Apache Software Foundation
>>>
>>> "What we have to learn to do, we learn by doing."
>>> -Aristotle
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.2.0-RC4 & Maven Wagon 1.0-beta-6
Posted by John Casey <jd...@commonjava.org>.
FWIW, the following URL at repository.apache.org includes the staging
repository for wagon:
https://repository.apache.org/content/groups/staging/
I've added this repository location to the group used by the Hudson
instance, and it's now building Maven 2.2.0-RC5-SNAPSHOT (the next
version on the maven-2.2.0-RC branch) successfully.
I'm not entirely sure how valuable it'd be to add the repository to the
POM in this branch, since we'll just have to remove it for the
vote...and since I was really hoping to vote for both projects at the
same time. If this is a major issue, I'm sure we can find a way to work
around it.
-john
Brett Porter wrote:
> I'll try and get some time to look through these, as I have some
> questions from what I've seen at a glance.
>
> It looks like you need to temporarily add the Wagon staging repo to the
> POM so that the hudson build will succeed though.
>
> - Brett
>
> On 23/06/2009, at 10:03 AM, John Casey wrote:
>
>> Hi everyone,
>>
>> As I'm sure you're aware, I've tried twice now to get a clean vote
>> done for Maven 2.2.0. In each case, we've run into blocking bugs that
>> have caused me to retract the vote and fix the code.
>>
>> Well, with the latest bug that Brian found, we're now dependent on
>> some configuration updates that are available on the trunk of Maven
>> Wagon. I've added configuration for the non-lightweight http wagon to
>> address:
>>
>> WAGON-270 - preemptive auth in non-lightweight http wagon causes
>> Unauthorized responses from some servers
>>
>> WAGON-264 - compressed tarball download problems
>>
>> WAGON-271 - Provide configurability of httpclient parameters to allow
>> user to tell Maven to ignore cookies
>>
>> The top issue relates to Brian's problem, and the bottom issue relates
>> to MNG-4165, which is also in the release notes for Maven 2.2.0. The
>> middle issue was a side-effect of fixing the other two.
>>
>> I'd like to have as many eyes on this release candidate as I can get.
>> I'm doing another RC instead of a new vote thread because I don't want
>> to push it too much and wind up with a profusion of different
>> artifacts in people's local repositories marked as being part of Maven
>> 2.2.0 when they are really part of failed votes for 2.2.0...
>>
>> Once I'm confident this RC is good to go, I'll call votes for both
>> Wagon 1.0-beta-6 and Maven 2.2.0.
>>
>> You can find the staging repositories here:
>>
>> Wagon:
>>
>> https://repository.apache.org/content/repositories/maven-staging-002/
>>
>> Maven 2.2.0-RC4:
>>
>> https://repository.apache.org/content/repositories/maven-staging-006/
>>
>>
>> You can find release notes here:
>>
>> Wagon:
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335&styleName=Html&version=15403
>>
>>
>> Maven:
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=15103
>>
>>
>>
>> Please give these a try, and let me know what you find!
>>
>> Thanks,
>>
>> -john
>>
>> ---
>> John Casey
>> Developer and PMC Member, Apache Maven (http://maven.apache.org)
>> Member, Apache Software Foundation
>>
>> "What we have to learn to do, we learn by doing."
>> -Aristotle
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.2.0-RC4 & Maven Wagon 1.0-beta-6
Posted by Brett Porter <br...@apache.org>.
I'll try and get some time to look through these, as I have some
questions from what I've seen at a glance.
It looks like you need to temporarily add the Wagon staging repo to
the POM so that the hudson build will succeed though.
- Brett
On 23/06/2009, at 10:03 AM, John Casey wrote:
> Hi everyone,
>
> As I'm sure you're aware, I've tried twice now to get a clean vote
> done for Maven 2.2.0. In each case, we've run into blocking bugs
> that have caused me to retract the vote and fix the code.
>
> Well, with the latest bug that Brian found, we're now dependent on
> some configuration updates that are available on the trunk of Maven
> Wagon. I've added configuration for the non-lightweight http wagon
> to address:
>
> WAGON-270 - preemptive auth in non-lightweight http wagon causes
> Unauthorized responses from some servers
>
> WAGON-264 - compressed tarball download problems
>
> WAGON-271 - Provide configurability of httpclient parameters to
> allow user to tell Maven to ignore cookies
>
> The top issue relates to Brian's problem, and the bottom issue
> relates to MNG-4165, which is also in the release notes for Maven
> 2.2.0. The middle issue was a side-effect of fixing the other two.
>
> I'd like to have as many eyes on this release candidate as I can
> get. I'm doing another RC instead of a new vote thread because I
> don't want to push it too much and wind up with a profusion of
> different artifacts in people's local repositories marked as being
> part of Maven 2.2.0 when they are really part of failed votes for
> 2.2.0...
>
> Once I'm confident this RC is good to go, I'll call votes for both
> Wagon 1.0-beta-6 and Maven 2.2.0.
>
> You can find the staging repositories here:
>
> Wagon:
>
> https://repository.apache.org/content/repositories/maven-staging-002/
>
> Maven 2.2.0-RC4:
>
> https://repository.apache.org/content/repositories/maven-staging-006/
>
>
> You can find release notes here:
>
> Wagon:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335&styleName=Html&version=15403
>
> Maven:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=15103
>
>
> Please give these a try, and let me know what you find!
>
> Thanks,
>
> -john
>
> ---
> John Casey
> Developer and PMC Member, Apache Maven (http://maven.apache.org)
> Member, Apache Software Foundation
>
> "What we have to learn to do, we learn by doing."
> -Aristotle
>
> ---------------------------------------------------------------------
> 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