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 2014/05/02 15:55:14 UTC
[jira] [Commented] (SLING-3538) Maven archetypes should use the
same port as the default launchpad port
[ https://issues.apache.org/jira/browse/SLING-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987709#comment-13987709 ]
Robert Munteanu commented on SLING-3538:
----------------------------------------
Fixed IT for the servlet archetype in http://svn.apache.org/viewvc?view=revision&revision=1591908
> Maven archetypes should use the same port as the default launchpad port
> -----------------------------------------------------------------------
>
> Key: SLING-3538
> URL: https://issues.apache.org/jira/browse/SLING-3538
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Affects Versions: Servlet Archetype 1.0.0, Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0, Initial Content Archetype 1.0.0
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Servlet Archetype 1.0.2, Bundle Archetype 1.0.2, JCRInstall Bundle Archetype 1.0.2, Initial Content Archetype 1.0.2
>
>
> The Maven archetypes should be usable out-of-the-box with a Sling launchpad. Right now deploying archetypes fails since the maven-sling-plugin is configured with port 8888 - which we typically use for integration tests - but the sling launchpad start by default on port 8080.
> I think more people would use port 8080 rather than 8888, so we should use that in our archetypes by default.
--
This message was sent by Atlassian JIRA
(v6.2#6252)