[
https://issues.apache.org/jira/browse/MRELEASE-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729610#comment-17729610
]
Herve Boutemy edited comment on MRELEASE-1129 at 6/6/23 6:34 AM:
-----------------------------------------------------------------
from experience doing Reproducible Builds, it varies based on the Maven version
used:
https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/doc/BUILDSPEC.md#avoid-http-vs-https-mavenxsd-url-difference-in-pom-generated-by-flatten-maven-plugin
are you using old Maven 3.6.2 or less for the release process? is it using
flatten-maven-plugin?
was (Author: hboutemy):
from experience doing Reproducible Builds, it varies based on the Maven version
used:
https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/doc/BUILDSPEC.md#avoid-http-vs-https-mavenxsd-url-difference-in-pom-generated-by-flatten-maven-plugin
are you using old Maven 3.6.2 or less for the release process?
> https POM URIs break the release plugin
> ---------------------------------------
>
> Key: MRELEASE-1129
> URL: https://issues.apache.org/jira/browse/MRELEASE-1129
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 3.0.1
> Reporter: Henning Schmiedehausen
> Priority: Major
> Fix For: waiting-for-feedback, wontfix-candidate
>
> Attachments: pom-after-transform.xml, pom.xml
>
>
> replacing the "http" URIs with "https" in the POM headers breaks the release
> process.
> When the pom gets prepared, the plugin rewrites the header back to "http" and
> adds an xmlns section to every opening tag in the POM creating an invalid POM.
> Sadly we are stuck with http:// URIs in the POMs for now.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
