Brings up two questions:

- Why is the lightweight wagon using Base64Encoder, aka a sun private class?
- There is a known valid workaround for a 10 years old bug. Why not using it?




2011/3/16 Tamás Cservenák <[email protected]>:
> Howdy,
>
> that's a known bug in JRE's base64 encoder, that is used when
> "lightweight" wagon is used to deploy (used by java.net.URL it powers
> this wagon). The Base64 encoder puts \n chars
>
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4615330
>
> Try to force maven to use some other wagon instead of the lightweight one.
>
>
> Thanks,
> ~t~
>
> On Fri, Mar 11, 2011 at 10:31 PM, Simone Tripodi
> <[email protected]> wrote:
>> Hi all guys,
>> I'm experiencing an issue when uploading artifacts on repo, details
>> follow below.
>> Does anyone has any hint/idea?
>> Many thanks in advance!
>> Simo
>>
>> ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy
>> (default-deploy) on project mybatis-parent: Failed to deploy
>> artifacts: Could not transfer artifact
>> org.mybatis:mybatis-parent:pom:10-20110311.210454-1 from/to
>> sonatype-nexus-snapshots
>> (https://oss.sonatype.org/content/repositories/snapshots):
>> java.lang.IllegalArgumentException: Illegal character(s) in message
>> header value: Basic
>> bXliYXRpcy1odWRzb246e2Q2Q05PeXZpS1d3SGQxN1pSNUZNMFlMMVZZcFVsemJCQzF4Wm81ajJw
>> [ERROR] Y2d0a2JvaDZYTTNCNHlsK0NpbVBsK2J9
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>



-- 
I Am What I Am And That's All What I Yam (Popeye)

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

Reply via email to