You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2013/09/12 17:40:53 UTC

[jira] [Resolved] (SLING-3056) [Tooling] Separate m2eclipse dependent extensions from others, in slingclipse

     [ https://issues.apache.org/jira/browse/SLING-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Egli resolved SLING-3056.
--------------------------------

    Resolution: Fixed

m2e-feature and eclipse-m2e-ui plugin added as a separation for this
                
> [Tooling] Separate m2eclipse dependent extensions from others, in slingclipse
> -----------------------------------------------------------------------------
>
>                 Key: SLING-3056
>                 URL: https://issues.apache.org/jira/browse/SLING-3056
>             Project: Sling
>          Issue Type: Improvement
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.0.0
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>
> At the moment slingclipse contains extensions which require m2eclipse plugin to be installed as a hard-dependency from slingclipse. These extensions should, as a minimum, be separated from the remaining extensions, such that the user can choose to install them or not. Technically, the separation will be bundled into a separate feature

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