[
https://issues.apache.org/jira/browse/SLING-12856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004679#comment-18004679
]
Robert Munteanu commented on SLING-12856:
-----------------------------------------
FWIW, I agree. The main thing we would 'lose' is code completion and navigation
in JSPs.
> Sling IDE: Do not enable WTP natures/facets for content-packages by default
> ---------------------------------------------------------------------------
>
> Key: SLING-12856
> URL: https://issues.apache.org/jira/browse/SLING-12856
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.2.2
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: Sling Eclipse IDE 1.3.0
>
>
> Currently when configuring a Maven project of type "content-package" there is
> WTP natures/facets set up automatically. Unfortunately a content-package is
> pretty far away from being a standard JEE/Servlet application. For example
> Eclipse automatically creates a MANIFEST.MF below the website root (which is
> set to the jcr_root folder). This is just plain wrong, so I would rather tend
> to not set that option by default and put a disclaimer into the dialog to
> enable that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
