[jira] [Commented] (MNGSITE-419) The instructions for creating a Maven project release need to be updated

2020-09-02 Thread Herve Boutemy (Jira)


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

Herve Boutemy commented on MNGSITE-419:
---

"you cannot use Java 7 because of TLS": not strictly true: see 
https://central.sonatype.org/articles/2018/May/04/discontinued-support-for-tlsv11-and-below/
= summary on Java 7: Java 7 supports TLS 1.2 but it is disabled by default in 
versions before 1.7.0_131-b31
then either you use Java 7 update 131 as a minimum and everything is ok = what 
I personally do
either you add "-Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2"

on using toolchains: my concern on using toolchains is that it makes 
reproducible builds checks a lot more complex, because it requires the 
rebuilder to create a setup with equivalent toolchains configuration

for example, supporting such a configuration in reproducible-central 
https://github.com/jvm-repo-rebuild/reproducible-central would bring in much 
complexity in the rebuild script and Docker images used

> The instructions for creating a Maven project release need to be updated
> 
>
> 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 
> 

[jira] [Commented] (MNGSITE-419) The instructions for creating a Maven project release need to be updated

2020-07-31 Thread Dennis Lundberg (Jira)


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

Dennis Lundberg commented on MNGSITE-419:
-

According to VCS history 3.2.3 is the first version which defaults to use https 
for central.

Java 7 and TLS 1.2 is a great example. There is not a definitive yes or no 
answer to this issue. There are options and opinions, and we should gather them 
here and discuss them.

> The instructions for creating a Maven project release need to be updated
> 
>
> 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 

[jira] [Commented] (MNGSITE-419) The instructions for creating a Maven project release need to be updated

2020-07-31 Thread Elliotte Rusty Harold (Jira)


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

Elliotte Rusty Harold commented on MNGSITE-419:
---

Some Java 7's do support TLS 1.2

 

https://www.baeldung.com/java-7-tls-v12

> The instructions for creating a Maven project release need to be updated
> 
>
> 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] 
> 

[jira] [Commented] (MNGSITE-419) The instructions for creating a Maven project release need to be updated

2020-07-31 Thread Elliotte Rusty Harold (Jira)


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

Elliotte Rusty Harold commented on MNGSITE-419:
---

What's the first version of Maven to support https artifact retrieval? It's 
probably safe to drop support for any version before that.

> The instructions for creating a Maven project release need to be updated
> 
>
> Key: MNGSITE-419
> URL: https://issues.apache.org/jira/browse/MNGSITE-419
> Project: Maven Project Web Site
>  Issue Type: Improvement
>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 

[jira] [Commented] (MNGSITE-419) The instructions for creating a Maven project release need to be updated

2020-07-31 Thread Hudson (Jira)


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

Hudson commented on MNGSITE-419:


Build succeeded in Jenkins: Maven TLP » maven-site » elharo-patch-6 #11

See 
https://builds.apache.org/job/maven-box/job/maven-site/job/elharo-patch-6/11/

> The instructions for creating a Maven project release need to be updated
> 
>
> Key: MNGSITE-419
> URL: https://issues.apache.org/jira/browse/MNGSITE-419
> Project: Maven Project Web Site
>  Issue Type: Improvement
>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