[
https://issues.apache.org/jira/browse/MRELEASE-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730842#comment-17730842
]
Michael Osipov commented on MRELEASE-1129:
------------------------------------------
[~hgschmie], there is only one namespace for the version 4.0.0 of the POM:
"http://maven.apache.org/POM/4.0.0";. Nothing else. Only we have the power to
modify it, not the user. {{xsi:schemaLocation}} is optional for validators,
they can also use an XML catalog to thesolve the XSD file from another
location, but still representing the same schema from the very same namespace.
While you can change the schema location you can *never* change the namespace
URI, not URL!
This is why the input is broken. Anything else is not valid and not a POM,
especially an XML file with unnamespaced elements. It must be either the
default namespace or a qualified namespace.
You should really read the XML in a nutshell from [~elharo], best money I spent
on an IT book.
> 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)
