maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Fox <bri...@infinity.nu>
Subject Re: [PLEASE TEST] Maven 2.2.0-RC4 & Maven Wagon 1.0-beta-6
Date Thu, 25 Jun 2009 12:52:13 GMT
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<joerg.schaible@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


Mime
View raw message