[
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:
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<id>replaceTextVersions</id>
<phase>none</phase>
<configuration>
<tasks>
<replace token= "${project.version}" value="${newVersion}"
dir="${basedir}">
<include name="apex-app-archetype/README.md"/>
<include name="apex-conf-archetype/README.md"/>
</replace>
</tasks>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
</plugin>
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
Thoughts?
> 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
(v6.3.4#6332)
