[
https://issues.apache.org/jira/browse/HBASE-24014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062034#comment-17062034
]
Nick Dimiduk commented on HBASE-24014:
--------------------------------------
{{maven-release-plugin:3.0.0-M1:update-versions}} looks like it's the latest
version.
Looks like there are https URLs to the XSD files listed on the
[faq|https://maven.apache.org/general.html#maven-xsd], but the namespaces
themselves are defined as http, [model
reference|http://maven.apache.org/ref/3.6.3/maven-model/maven.html].
Seems like {{org.codehaus.mojo:versions-maven-plugin:2.7:set}} handles our poms
without modification; maybe I can use this for now. It looks less maintained
than the release plugin though.
> https in xmlns URIs breaks maven-release-plugin:update-versions
> ---------------------------------------------------------------
>
> Key: HBASE-24014
> URL: https://issues.apache.org/jira/browse/HBASE-24014
> Project: HBase
> Issue Type: Bug
> Components: build
> Affects Versions: 2.3.0, 2.4.0
> Reporter: Nick Dimiduk
> Priority: Major
>
> Trying to use {{mvn release:update-versions}} to update our version on
> {{branch-2}}, getting
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:update-versions
> (default-cli) on project hbase: Execution default-cli of goal
> org.apache.maven.plugins:maven-release-plugi
> n:3.0.0-M1:update-versions failed: The namespace
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; could not be added as a
> namespace to "project": The namespace prefix "xsi" collides with an
> additional na
> mespace declared by the element -> [Help 1]
> {noformat}
> Looks like it's because these xmlns values have actual meaning to the plugin,
> and having https uris breaks things. Removing the https bits allows the
> plugin to proceed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
