[
https://issues.apache.org/jira/browse/OOZIE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200241#comment-13200241
]
Prakhar Sharma commented on OOZIE-679:
--------------------------------------
For an automated process (like CI builds) to do mvn versions:set
-DnewVersion=123 one can either write a new script, or move that function in
bin/mkdistro.sh. I chose to do the later. With this change, you pass
-DnewVersion=123 as first argument to bin/mkdistro.sh. It first changes
version#s and then starts the build.
> changes to pom.xml's and bin/mkdistro.sh to manage version#'s for better
> build automation
> ------------------------------------------------------------------------------------------
>
> Key: OOZIE-679
> URL: https://issues.apache.org/jira/browse/OOZIE-679
> Project: Oozie
> Issue Type: Improvement
> Reporter: Prakhar Sharma
> Labels: build,, ci
>
> Right now automation of Oozie build is difficult as there is no (easy) way to
> programmitcally change version# in pom.xml files. This jira is to address
> this issue. Mainly to make changes in pom.xml and build files
> (bin/mkdistro.sh) so that version# can be controlled through the use of maven
> versions plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
