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 2015/11/12 12:41:11 UTC

[jira] [Closed] (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 closed SLING-3056.
------------------------------

> [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
>             Fix For: Discovery Impl 1.0.2
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)