[
https://issues.apache.org/jira/browse/APEXCORE-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884918#comment-15884918
]
ASF GitHub Bot commented on APEXCORE-655:
-----------------------------------------
GitHub user tweise opened a pull request:
https://github.com/apache/apex-core/pull/480
APEXCORE-655 Support archetypeVersion=LATEST when generating project.
@davidyan74 please review
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tweise/apex-core APEXCORE-655
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-core/pull/480.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #480
----
commit bc563189f627c31db4a5ff5bec1924bb7df6f3e2
Author: Thomas Weise <[email protected]>
Date: 2017-02-26T21:29:14Z
APEXCORE-655 Support archetypeVersion=LATEST when generating project.
----
> Support LATEST as archetype version when creating a project
> ------------------------------------------------------------
>
> Key: APEXCORE-655
> URL: https://issues.apache.org/jira/browse/APEXCORE-655
> Project: Apache Apex Core
> Issue Type: Improvement
> Reporter: Thomas Weise
>
> Rather than keep on replacing the Apex archetype version number in various
> examples, Maven supports LATEST to refer to the latest released archetype
> version.
> This requires a change to decouple resolution of Apex dependency version from
> archetype version to replace the Apex version when the archetype is created
> vs. when the project is created.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
