apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Weise (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-655) Support LATEST as archetype version when creating a project
Date Sun, 26 Feb 2017 21:22:46 GMT

    [ 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:

mvn archetype:generate \
 -DarchetypeGroupId=org.apache.apex \
 -DarchetypeArtifactId=apex-app-archetype -DarchetypeVersion=LATEST \
 -DgroupId=com.example -Dpackage=com.example.myapexapp -DartifactId=myapexapp \

> 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

This message was sent by Atlassian JIRA

View raw message