[
https://issues.apache.org/jira/browse/SLING-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15589038#comment-15589038
]
Georg Henzler commented on SLING-6175:
--------------------------------------
[~rombert], you stated
bq. {{M2E_USE_WTP_PROJECT_SETUP}} - remove, but default to using it. This (at
least) makes more file types appare in the New... menu and is probably closed
to what we want in terms of use experience
in
[SLING-3100|https://issues.apache.org/jira/browse/SLING-3100?focusedCommentId=15169067&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15169067].
With JSP being the main language for templates I also thought it was a good
idea to be close to WTP back then, but with HTL today I agree with [~kwin] that
it's better to not use it anymore. WDYT?
> Sling IDE: Don't configure WTP natures by default for content-package projects
> ------------------------------------------------------------------------------
>
> Key: SLING-6175
> URL: https://issues.apache.org/jira/browse/SLING-6175
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.1.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
>
> With the configurator being added in SLING-3100 there is always WTP natures
> and according facets added for {{content-package}} projects. This is not
> always desired.
> It e.g. leads to the fact that a META-INF/MANIFEST.MF is automatically
> generated below the jcr_root folder
> (https://wiki.eclipse.org/M2E-WTP_FAQ#What_is_this_web_resources_folder.3F).
> Since {{content-packages}} are quite different from {{war}} projects I would
> propose to only add those natures/facets if this is explicitly
> configured/requested. Otherwise we should only add the native Sling IDE
> natures/facets.
> Apart from that some validators are triggered during the build which are
> really time consuming.
> The original idea behind making a {{content-package}} similar to a {{war}}
> was to support code assist in JSPs better (i.e. for tag libraries). This
> never reliably worked and therefore we should rather get rid of that approach.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
