[
https://issues.apache.org/jira/browse/SLING-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020022#comment-14020022
]
Konrad Windszus edited comment on SLING-3651 at 6/6/14 4:45 PM:
----------------------------------------------------------------
What would be good to do as well, is to reuse the same dialog with the tree
view for the Sling Property Page (because the improved one only shows
containers below the current project and gives out validation information).
[~rombert] Maybe you can do that. Otherwise we can defer that part to a future
version.
was (Author: kwin):
What would be good to do as well, is to reuse the same dialog with the tree
view for the Sling Property Page (because it only shows containers below the
project and gives out validation information). [~rombert] Maybe you can do
that. Otherwise we can defer that part to a future version.
> 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
>
> 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)
