apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chinmay Kolhatkar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-34) Fix version number replacement
Date Fri, 08 Jan 2016 18:39:39 GMT

    [ https://issues.apache.org/jira/browse/APEXCORE-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089662#comment-15089662

Chinmay Kolhatkar commented on APEXCORE-34:

One possible solution here is to have a unbound plugin to any phase in apex top level pom.xml
as follows:

                <replace token= "${project.version}" value="${newVersion}" dir="${basedir}">
                  <include name="apex-app-archetype/README.md"/>
                  <include name="apex-conf-archetype/README.md"/>

The way to execute this is:
mvn antrun:run@replaceTextVersions -DnewVersion=3.4.0-incubating-SNAPSHOT

This would have a cleaner way to change the versions in text files.

So overall the steps to upgrade the version would look like this:
mvn antrun:run@replaceTextVersions -DnewVersion=3.4.0-incubating-SNAPSHOT
mvn versions:set -DnewVersion=3.4.0-incubating-SNAPSHOT 


> Fix version number replacement
> ------------------------------
>                 Key: APEXCORE-34
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-34
>             Project: Apache Apex Core
>          Issue Type: Task
>            Reporter: Thomas Weise

This message was sent by Atlassian JIRA

View raw message