[
https://issues.apache.org/jira/browse/MRELEASE-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729707#comment-17729707
]
Herve Boutemy commented on MRELEASE-1129:
-----------------------------------------
notice that I now understood the issue: it's about the xmlns URI, i.e.
xmlns="http://maven.apache.org/POM/4.0.0";
not what i saw in Reproducible Builds, which is a real URL = the URL of the xsd
= https://maven.apache.org/xsd/maven-4.0.0.xsd
[~hgschmie]what is the interest of changing the xmlns URI?
it's an immutable identifier
like xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; which can't be
replaced with https and would not bring any benefit AFAIK
> https POM xmlns 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)
