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:29:14 UTC

[jira] [Closed] (SLING-3651) Improve Conversion To Bundle and Content Projects

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

Stefan Egli closed SLING-3651.
------------------------------

> Improve Conversion To Bundle and Content Projects
> -------------------------------------------------
>
>                 Key: SLING-3651
>                 URL: https://issues.apache.org/jira/browse/SLING-3651
>             Project: Sling
>          Issue Type: Bug
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.0.0
>            Reporter: Konrad Windszus
>            Assignee: Stefan Egli
>             Fix For: Sling Eclipse IDE 1.0.0
>
>
> Currently the "Convert To Bundle Project" is always enabled and I can even add the bundle facet to a maven project which is of packaging "content-package"
> The "Convert To Content Project..." is only enabled under very specific conditions. Currently those conditions are neither described in https://cwiki.apache.org/confluence/display/SLING/Sling+IDE+tooling+User+Guide nor is there some warning/trace messages available. 
> I would suggest the following:
> Always enable both conversion actions. Display a warning message with a very descriptive warning in case the conversion cannot be performed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)