2.2.1 is fine on that regard

On Fri, Nov 5, 2010 at 19:13, Howard Lewis Ship <[email protected]> wrote:
> I hope 2.2.1 generates proper checksums because upgrading to 3.x was a
> floster cuck for me.
>
> On Fri, Nov 5, 2010 at 12:49 AM, Ulrich Stärk <[email protected]> wrote:
>
>> FYI
>>
>> -------- Original Message --------
>> Subject: [jira] Created: (INFRA-3151) add servlet filter to nexus to block
>> maven 2.2.0 deploys
>> Date: Wed, 3 Nov 2010 19:37:22 -0400 (EDT)
>> From: Brian Fox (JIRA) <[email protected]>
>> Reply-To: [email protected]
>> To: [email protected]
>>
>> add servlet filter to nexus to block maven 2.2.0 deploys
>> --------------------------------------------------------
>>
>>                 Key: INFRA-3151
>>                 URL: https://issues.apache.org/jira/browse/INFRA-3151
>>             Project: Infrastructure
>>          Issue Type: Improvement
>>      Security Level: public (Regular issues)
>>          Components: Nexus
>>            Reporter: Brian Fox
>>            Assignee: Brian Fox
>>
>>
>> Maven 2.2.0 is known to produce bad checksums and doubles the data upload
>> potentially causing timeouts.
>>
>> Here's an example user agent we want to block: Apache-Maven/2.2 (Java
>> 1.6.0_16; Linux 2.6.26-2-amd64) maven-artifact/2.2.0" "-"
>>
>> This should be blocked from /content for PUTs only.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to learn
> how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>



-- 
Andreas Andreou - [email protected] - http://blog.andyhot.gr
Tapestry PMC / Tacos developer
Open Source / JEE Consulting

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to