You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2025/09/25 10:25:00 UTC

[jira] [Closed] (SLING-12856) Sling IDE: Do not enable WTP natures/facets for content-packages by default

     [ https://issues.apache.org/jira/browse/SLING-12856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu closed SLING-12856.
-----------------------------------

> 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
>            Assignee: 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/web 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)