[SLING-5634] Content projects automatically configured as WST projects fail to deploy

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Sling Eclipse IDE 1.0.10
• Fix Version/s: Sling Eclipse IDE 1.2.0
• Component/s: IDE
• Assignee: Robert Munteanu
• Reporter: Robert Munteanu
• Created: 01/Apr/16 13:16
• Updated: 21/Jan/18 20:23
• Resolved: 01/Apr/16 13:27

Description

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"

Issue Links

• relates to: SLING-3100 Provide a m2e project configurator for packaging "content-package"
• links to: AEM Eclipse dev tools issue #67