You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2015/10/15 21:40:05 UTC
[jira] [Commented] (SLING-5156) Create a Maven archetype building a
slingstart application
[ https://issues.apache.org/jira/browse/SLING-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14959487#comment-14959487 ]
Robert Munteanu commented on SLING-5156:
----------------------------------------
* [r1708876|https://svn.apache.org/r1708876] - initial version of the archetype
* [r1708877|https://svn.apache.org/r1708877] - added to the main reactor pom
> Create a Maven archetype building a slingstart application
> ----------------------------------------------------------
>
> Key: SLING-5156
> URL: https://issues.apache.org/jira/browse/SLING-5156
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Slingstart Archetype 1.0.0
>
>
> Since the slingstart packaging has superseeded the launchpad we should have an archetype which reflects that. Since the slingstart-maven-plugin is able to create both a standalone launcher and a WAR file we should not convert the old launchpad archetypes, but rather create a new archetype which uses the slingstart packaging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)