[
https://issues.apache.org/jira/browse/HBASE-24014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062955#comment-17062955
]
Nick Dimiduk commented on HBASE-24014:
--------------------------------------
I think the only place we can have https in the {{project}} element is in the
URI to the xsd file, so
{noformat}
<project xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd";>
{noformat}
> 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)
