[
https://issues.apache.org/jira/browse/FLINK-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823168#comment-15823168
]
ASF GitHub Bot commented on FLINK-5489:
---------------------------------------
Github user rmetzger commented on the issue:
https://github.com/apache/flink/pull/3123
Good change. Thank you.
I'll merge it right away
> maven release:prepare fails due to invalid JDOM comments in pom.xml
> -------------------------------------------------------------------
>
> Key: FLINK-5489
> URL: https://issues.apache.org/jira/browse/FLINK-5489
> Project: Flink
> Issue Type: Bug
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Priority: Minor
> Labels: newbie
>
> When I was trying to publish Flink to our internal artifactory, I found out
> that {{maven release:prepare}} has failed because the plugin complains about
> the some of the comments pom.xml do not conform with the JDOM format:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare (default-cli) on
> project flink-parent: Execution default-cli of goal
> org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare failed: The data
> "-
> [ERROR] This module is used a dependency in the root pom. It activates
> shading for all sub modules
> [ERROR] through an include rule in the shading configuration. This assures
> that Maven always generates
> [ERROR] an effective pom for all modules, i.e. get rid of Maven properties.
> In particular, this is needed
> [ERROR] to define the Scala version property in the root pom but not let the
> root pom depend on Scala
> [ERROR] and thus be suffixed along with all other modules.
> [ERROR] " is not legal for a JDOM comment: Comment data cannot start with a
> hyphen.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
