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/04/30 16:49:14 UTC
[jira] [Updated] (SLING-3532) Move sling plugin configuration out
of the autoInstallBundle profile
[ https://issues.apache.org/jira/browse/SLING-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu updated SLING-3532:
-----------------------------------
Fix Version/s: JCRInstall Bundle Archetype 1.0.2
Bundle Archetype 1.0.2
> Move sling plugin configuration out of the autoInstallBundle profile
> --------------------------------------------------------------------
>
> Key: SLING-3532
> URL: https://issues.apache.org/jira/browse/SLING-3532
> 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
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Servlet Archetype 1.0.2, Bundle Archetype 1.0.2, JCRInstall Bundle Archetype 1.0.2
>
>
> The maven-sling-plugin is configured completely inside a profile block. This means that it's not available for 'regular' executions, e.g. mvn sling:install .
> The fix is simple - move the plugin configuration to the plugins section, and only bind the execution in the profile.
--
This message was sent by Atlassian JIRA
(v6.2#6252)