Mailing-List: contact dev-help@apex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.apache.org
Date: Sun, 26 Feb 2017 21:22:46 +0000 (UTC)
From: "Thomas Weise (JIRA)" <jira@apache.org>
To: dev@apex.incubator.apache.org
Message-ID: <JIRA.13046504.1488143909000.1309.1488144166009@Atlassian.JIRA>
In-Reply-To: <JIRA.13046504.1488143909000@Atlassian.JIRA>
References: <JIRA.13046504.1488143909000@Atlassian.JIRA> <JIRA.13046504.1488143909621@jira-lw-us.apache.org>
Subject: [jira] [Commented] (APEXCORE-655) Support LATEST as archetype
 version when creating a project
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 26 Feb 2017 21:22:55 -0000


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

Thomas Weise commented on APEXCORE-655:
---------------------------------------

Example for use of LATEST vs. specific version number:

{code}
mvn archetype:generate \
 -DarchetypeGroupId=org.apache.apex \
 -DarchetypeArtifactId=apex-app-archetype -DarchetypeVersion=LATEST \
 -DgroupId=com.example -Dpackage=com.example.myapexapp -DartifactId=myapexapp \
 -Dversion=1.0-SNAPSHOT
{code}

> 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)