[
https://issues.apache.org/jira/browse/SLING-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli resolved SLING-3073.
--------------------------------
Resolution: Fixed
Removed those comments, and also removed another usage of 'mvn install' - which
was needed initially before the vault-content-sync was implemented (due to a
dependency between an archetype-generated project and another one). Now there
is only one usage of the MavenLaunchHelper left: that's the one doing a
sling:install for a bundle project, if the tooling.support.install bundle is
not used/installed/configured.
> Do not create maven launch config for content-package packaging types
> ---------------------------------------------------------------------
>
> Key: SLING-3073
> URL: https://issues.apache.org/jira/browse/SLING-3073
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Reporter: Robert Munteanu
> Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> Creating such a launch config will not be useful once we finish vlt
> integration ( see SLING-2989 ) and will be removed afterwards.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
