[
https://issues.apache.org/jira/browse/MRELEASE-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731300#comment-17731300
]
Henning Schmiedehausen commented on MRELEASE-1129:
--------------------------------------------------
[~elharo] Thanks for the explanation. This is much more useful than a toxic
"shit in, shit out" comment.
I feel maven should in that case fail at pom loading time if the root namespace
identifier is not the expected (or one of the expected in the future) values.
The fact that most of maven works with the pom example I gave (basically
everything but releasing) makes me wonder how many invalid poms are out there.
> 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)
