[
https://issues.apache.org/jira/browse/MRELEASE-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730981#comment-17730981
]
Michael Osipov edited comment on MRELEASE-1129 at 6/9/23 2:20 PM:
------------------------------------------------------------------
This is one of the reasons I don't like using URLs for namespace at all. People
don't understand it. I prefer URNs solely, e.g., {{urn:apache.org:maven:...}}
was (Author: michael-o):
This is one of the reasons I don't like using URLs for namespace at all. People
don't understand it. I prefer URNs solely, e.g., {{{urn:apache.org:maven:...}}
> 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
> 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)
