[
https://issues.apache.org/jira/browse/SLING-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli resolved SLING-3651.
--------------------------------
Resolution: Fixed
Applied patch from [~kwin], thanks a lot!
I've adjusted the patch slightly to not show the action when a project is
already a content or a bundle project. IMO this is reasonably understandable
(that a project can either be a content or a bundle project, not both. And we
dont support automatic conversion from one to the other atm, that has to be
done manually via facet fiddlings). i've also provided some more details as to
which projects are listed in the 'convert to bundle project' wizard.
Marking this resolved, please let me know if this is fine for you, [~kwin],
otherwise feel free to reopen and comment accordingly.
> 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.2#6252)
