[
https://issues.apache.org/jira/browse/MRELEASE-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730827#comment-17730827
]
Herve Boutemy commented on MRELEASE-1129:
-----------------------------------------
{quote}Is there a hard requirement somewhere documented that the root namespace
identifier must be the "http://maven.apache.org/POM/4.0.0"; URI ?
{quote}
I don't know if this is written anywhere like this
I don't know if this is intentional or not
What I know is that it's used everywhere, for example
[https://maven.apache.org/ref/3.9.2/maven-model/maven.html], and I don't see
any interest into changing the Maven POM URI when using it
I don't know what is the general best practice about such xmlns URIs, as I
confess I'm not a XML Schema expert.
Reading the spec
[https://www.w3.org/TR/xmlschema-1/#Instance_Document_Constructions],
{quote}The XML representation of schema components uses a vocabulary identified
by the namespace name [http://www.w3.org/2001/XMLSchema].
{quote}
the spec seems to say that each schema has a URI that should not be customized
by users, but defined as the original schema provider has defined, which seems
logical as it helps tools everywhere to map URI identifiers to specific
semantics (which triggers now my old memory about XML and XML Schema when it
was introduced in 2000's)
which looks like what has been done at Maven level
then AFAIK, our implementation is not an unintended limitation but de-facto an
implementation of normal best practices about XML Schema and URIs (even without
citing them precisely)
> 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)
