[SLING-3100] Provide a m2e project configurator for packaging "content-package"

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Sling Eclipse IDE 1.0.0
• Fix Version/s: Sling Eclipse IDE 1.1.0
• Component/s: IDE
• Assignee: Robert Munteanu
• Reporter: Konrad Windszus
• Created: 24/Sep/13 09:17
• Updated: 20/Sep/17 13:12
• Resolved: 03/Mar/16 13:47

Description

To set up the appropriate project configuration just from the POM an according m2e project configurator is needed (http://wiki.eclipse.org/M2E_plugin_execution_not_covered#delegate_to_a_project_configurator_.28recommended.29)

The m2e-war-plugin comes with a project configurator which works also for content-packages pretty well but it is currently hard to reuse for any other packaging than "war" (due to the delegate pattern being used internally, compare with https://bugs.eclipse.org/bugs/show_bug.cgi?id=412213). Only if the project is having the dynamic web project facet the following features in Eclipse are supported:

• JSP include directives (considered for validation and supports ctrl+click to open linked file)
• Tag Library Support ( http://wiki.eclipse.org/WTP_FAQ#Why_isn.27t_the_JSP_editor.2Fvalidator_finding_my_custom_tag_libraries.3F )
• probably other features as well.

Apart from that a feature like overlays should be supported ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=384154 ), as often content-package projects are referencing JSPs from other projects, and the IDE needs to know those, to complete the validation.

Issue Links

• is related to: SLING-5634 Content projects automatically configured as WST projects fail to deploy
• is related to: SLING-6128 Sling IDE: Remove Lifecycle Mapping Extension Point for content-package
• is related to: SLING-6175 Sling IDE: Allow to disable WTP natures/facets for content-package projects
• relates to: SLING-3612 Provide a m2e project configurator for packaging "bundle"