maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herve Boutemy (Jira)" <j...@apache.org>
Subject [jira] [Commented] (MNGSITE-419) The instructions for releasing a Maven project need to be updated for JDK 7 because of TLS1.2 for central
Date Mon, 07 Sep 2020 22:17:00 GMT

    [ https://issues.apache.org/jira/browse/MNGSITE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191871#comment-17191871
] 

Herve Boutemy commented on MNGSITE-419:
---------------------------------------

"not caught by animal sniffer or the compiler"? really?
notice: Animal Sniffer is expected to detect such issues, but not fix, then it's only half
of the solution
but the compiler solution is expected to avoid such situation: I'm really suprised

> The instructions for releasing a Maven project need to be updated for JDK 7 because of
TLS1.2 for central
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: MNGSITE-419
>                 URL: https://issues.apache.org/jira/browse/MNGSITE-419
>             Project: Maven Project Web Site
>          Issue Type: Bug
>            Reporter: Dennis Lundberg
>            Priority: Major
>
> When I released maven-shared-utils I stumbled across a couple of things in our instructions
that needs to be updated.
> https://maven.apache.org/developers/release/maven-project-release-procedure.html
> The examples below are run using an empty local repository.
> *You cannot use Maven 3.0.5 any longer, because Maven central requires HTTPS*
> https://blog.sonatype.com/central-repository-moving-to-https
> {noformat}
> G:\git\apache\maven-filtering>mvn -version
> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100)
> Maven home: C:\Program Files\apache-maven-3.0.5
> Java version: 1.8.0_202, vendor: AdoptOpenJdk
> ...
> {noformat}
> {noformat}
> G:\git\apache\maven-filtering>mvn clean
> [INFO] Scanning for projects...
> Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-shared-components/34/maven-shared-components-34.pom
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR]   The project org.apache.maven.shared:maven-filtering:3.2.0-SNAPSHOT (G:\git\apache\maven-filtering\pom.xml)
has 1 error
> [ERROR]     Non-resolvable parent POM: Could not transfer artifact org.apache.maven.shared:maven-shared-components:pom:34
from/to central (http://repo.maven.apache.org/maven2): Failed to transfer file: http://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-shared-components/34/maven-shared-components-34.pom.
Return code is: 501 , ReasonPhrase:HTTPS Required. and 'parent.relativePath' points at wrong
local POM @ line 23, column 11 -> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the
following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> {noformat}
> Solution
> I used Maven 3.3.9. According to VCS history 3.2.3+ should work.
> *You cannot use Java 7, because Maven central requires TLS 1.2+*
> https://blog.sonatype.com/enhancing-ssl-security-and-http/2-support-for-central
> https://central.sonatype.org/articles/2018/May/04/discontinued-support-for-tlsv11-and-below/
> {noformat}
> G:\git\apache\maven-filtering>mvn -version
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: C:\Program Files\apache-maven-3.3.9
> Java version: 1.7.0_79, vendor: Oracle Corporation
> ...
> {noformat}
> {noformat}
> G:\git\apache\maven-filtering>mvn clean
> [INFO] Scanning for projects...
> Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-shared-components/34/maven-shared-components-34.pom
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-resolvable parent POM for org.apache.maven.shared:maven-filtering:3.2.0-SNAPSHOT:
Could not transfer artifact org.apache.maven.shared:maven-shared-components:pom:34 from/to
central (https://repo.maven.apache.org/maven2): Received fatal alert: protocol_version and
'parent.relativePath' points at wrong local POM @ line 23, column 11
>  @
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR]   The project org.apache.maven.shared:maven-filtering:3.2.0-SNAPSHOT (G:\git\apache\maven-filtering\pom.xml)
has 1 error
> [ERROR]     Non-resolvable parent POM for org.apache.maven.shared:maven-filtering:3.2.0-SNAPSHOT:
Could not transfer artifact org.apache.maven.shared:maven-shared-components:pom:34 from/to
central (https://repo.maven.apache.org/maven2): Received fatal alert: protocol_version and
'parent.relativePath' points at wrong local POM @ line 23, column 11 -> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the
following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> {noformat}
> Solution 1
> Use Java 8 with toolchains
> mvn release:prepare -Pjdk-toolchain
> Solution 2
> Add protocols on the command line
> mvn release:prepare -Dhttps.protocols=TLSv1.2
> *No instructions for using toolchains*
> For my release I went with solution 1, and it took me a while to figure out which combination
of command line switches to use. Here's what finally worked for me.
> {noformat}
> mvn release:prepare -Pjdk-toolchain
> mvn release:perform -DreleaseProfiles=apache-release,jdk-toolchain -Papache-release,jdk-toolchain
> {noformat}
> and then for the site
> {noformat}
> mvn -Preporting,jdk-toolchain site site:stage
> mvn scm-publish:publish-scm
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message