You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Jing Zhao (JIRA)" <ji...@apache.org> on 2017/03/30 20:31:42 UTC
[jira] [Comment Edited] (RATIS-57) Fix pom.xml for mvn
release:prepare
[ https://issues.apache.org/jira/browse/RATIS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949748#comment-15949748 ]
Jing Zhao edited comment on RATIS-57 at 3/30/17 8:31 PM:
---------------------------------------------------------
[~enis], I guess the purpose of the this patch is the following step in the Apache doc?
{code}
Diff the original file pom.xml with the one called pom.xml.tag to see if the license or any other info has been removed. This has been known to happen if the starting <project> tag is not on a single line. The only things that should be different between these files are the <version> and <scm> elements. Any other changes you must backport yourself to the original pom.xml file and commit before proceeding with the release.
{code}
was (Author: jingzhao):
I guess the purpose of the this patch is the following step in the Apache doc?
{code}
Diff the original file pom.xml with the one called pom.xml.tag to see if the license or any other info has been removed. This has been known to happen if the starting <project> tag is not on a single line. The only things that should be different between these files are the <version> and <scm> elements. Any other changes you must backport yourself to the original pom.xml file and commit before proceeding with the release.
{code}
> Fix pom.xml for mvn release:prepare
> -----------------------------------
>
> Key: RATIS-57
> URL: https://issues.apache.org/jira/browse/RATIS-57
> Project: Ratis
> Issue Type: Sub-task
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Attachments: r57_20170330.patch
>
>
> According to [Prepare your POMs for release|http://www.apache.org/dev/publishing-maven-artifacts.html#prepare-poms], the following command can test the pom.
> {code}
> mvn release:prepare -DdryRun=true -DautoVersionSubmodules=true
> {code}
> The JIRA is to fix the unexpected diff between pom.xml and pom.xml.tag.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)