[
https://issues.apache.org/jira/browse/SLING-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221680#comment-15221680
]
Robert Munteanu commented on SLING-5634:
----------------------------------------
Fixed in [r1737378|https://svn.apache.org/r1737378]
> Content projects automatically configured as WST projects fail to deploy
> ------------------------------------------------------------------------
>
> Key: SLING-5634
> URL: https://issues.apache.org/jira/browse/SLING-5634
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.0.10
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.1.2
>
>
> With SLING-3100 content packages are automatically configured as Dynamic Web
> Projects if the {{content-package-maven-plugin}} is detected. In turn, this
> causes them to receive a jst.web facet.
> Given that our module factory and the other module factories have the same
> {{order}} ( -1 ), which module factory "wins" and determines the module type
> is not defined. Therefore, sometimes the modules are created as {{jst.web}}
> modules ( return value from {{IModule#getModuleType()}} and can't be deployed
> on a launchpad instance.
> The typical error is "The server does not support version 2.4 of the J2EE Web
> module specification"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
