[
https://jira.codehaus.org/browse/MNG-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317713#comment-317713
]
Olivier Lamy commented on MNG-5363:
-----------------------------------
Can I exactly know the env needed to reproduce this issue ?
I just deployed a project to https://oss.sonatype.org
My env
{code}
Apache Maven 3.1-SNAPSHOT (57d9c68e56a4bc8d825c7615534023eeda52b9c0; 2013-01-05
00:17:48+0100)
Maven home: /Users/olamy/softs/maven/trunk
Java version: 1.7.0_10, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_10.jdk/Contents/Home/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "mac os x", version: "10.8.2", arch: "x86_64", family: "mac"
{code}
{code}
Downloading:
https://oss.sonatype.org/content/repositories/snapshots/com/google/code/maven-scm-provider-svnjava/maven-scm-provider-svnjava/2.0.6-SNAPSHOT/maven-metadata.xml
Uploading:
https://oss.sonatype.org/content/repositories/snapshots/com/google/code/maven-scm-provider-svnjava/maven-scm-provider-svnjava/2.0.6-SNAPSHOT/maven-scm-provider-svnjava-2.0.6-20130119.211246-1.jar
Uploaded:
https://oss.sonatype.org/content/repositories/snapshots/com/google/code/maven-scm-provider-svnjava/maven-scm-provider-svnjava/2.0.6-SNAPSHOT/maven-scm-provider-svnjava-2.0.6-20130119.211246-1.jar
(57 KB at 14.0 KB/sec)
Uploading:
https://oss.sonatype.org/content/repositories/snapshots/com/google/code/maven-scm-provider-svnjava/maven-scm-provider-svnjava/2.0.6-SNAPSHOT/maven-scm-provider-svnjava-2.0.6-20130119.211246-1.pom
Uploaded:
https://oss.sonatype.org/content/repositories/snapshots/com/google/code/maven-scm-provider-svnjava/maven-scm-provider-svnjava/2.0.6-SNAPSHOT/maven-scm-provider-svnjava-2.0.6-20130119.211246-1.pom
(10 KB at 1.1 KB/sec)
Downloading:
https://oss.sonatype.org/content/repositories/snapshots/com/google/code/maven-scm-provider-svnjava/maven-scm-provider-svnjava/maven-metadata.xml
Downloaded:
https://oss.sonatype.org/content/repositories/snapshots/com/google/code/maven-scm-provider-svnjava/maven-scm-provider-svnjava/maven-metadata.xml
(328 B at 0.1 KB/sec)
Uploading:
https://oss.sonatype.org/content/repositories/snapshots/com/google/code/maven-scm-provider-svnjava/maven-scm-provider-svnjava/2.0.6-SNAPSHOT/maven-metadata.xml
Uploaded:
https://oss.sonatype.org/content/repositories/snapshots/com/google/code/maven-scm-provider-svnjava/maven-scm-provider-svnjava/2.0.6-SNAPSHOT/maven-metadata.xml
(818 B at 0.2 KB/sec)
Uploading:
https://oss.sonatype.org/content/repositories/snapshots/com/google/code/maven-scm-provider-svnjava/maven-scm-provider-svnjava/maven-metadata.xml
Uploaded:
https://oss.sonatype.org/content/repositories/snapshots/com/google/code/maven-scm-provider-svnjava/maven-scm-provider-svnjava/maven-metadata.xml
(368 B at 0.1 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
{code}
> Regression for SSLv3
> --------------------
>
> Key: MNG-5363
> URL: https://jira.codehaus.org/browse/MNG-5363
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Errors
> Affects Versions: 3.0.4
> Environment: Operation system independent, but tested on Macbook Pro
> with 10.6 and Red Hat Enterprise Linux 6 on a virtual machine.
> Reporter: James Kionka
> Priority: Critical
>
> When attempting to access a Maven repository which uses SSLv3, you get the
> following error, "javax.net.ssl.SSLException: Received fatal alert:
> bad_record_mac".
> Earlier versions of Maven used java.net.URLConnection which respects the
> https.protocols system property. This allowed us to set it to SSLv3, which is
> what our Maven repository uses. However, HttpClient ignores that property. In
> other situations, we programmatically tell HttpClient to use SSLv3, which we
> cannot do from our end.
> You can find another person in the same situation here:
> http://stackoverflow.com/questions/12787657/received-fatal-alert-bad-record-mac-when-deploying-to-sonatype
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
