[
https://issues.apache.org/jira/browse/SLING-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019714#comment-14019714
]
Konrad Windszus edited comment on SLING-3651 at 6/6/14 9:43 AM:
----------------------------------------------------------------
Also I would like if the ProjectHelper.getInferredContentProjectContentRoot()
would only be taken as the default for the dialog (asking for the JCR-Root).
But it should be possible to convert projects, even if the JCR-Root is outside
the checked folders. In some projects the jcr_root is at /src/main/jcr_root.
was (Author: kwin):
Also I would like if the ProjectHelper.getInferredContentProjectContentRoot()
would only be taken as the default for the dialog (asking for the JCR-Root).
But it should be possible to convert projects, even if the JCR-Root is outside
the checked folders. In some project the jcr_root is at /src/main/jcr_root.
> 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)
