[FELIX-3358] Enhance the maven-scr-plugin to be compatible with recent Maven/Eclipse integrations

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: maven-scr-plugin-1.8.0
• Fix Version/s: maven-scr-plugin-1.9.0
• Component/s: SCR Tooling
• Environment: Eclipse Indigo or newer
• Assignee: Carsten Ziegeler
• Reporter: Robert Munteanu
• Created: 21/Feb/12 07:52
• Updated: 07/Dec/12 10:25
• Resolved: 28/Nov/12 15:51

Description

With the recent changes brought to the Maven Eclipse integration, any unknown [0] plugins are flagged as problematic and an error is reported in the pom.xml . Typically this is solved by writing a thin integration layer between the Eclipse integration and the Maven plugin [1] or by instructing Eclipse to ignore some plugin executions.

The new 1.1 version of the m2eclipse plugin will allow a Maven plugin ( with no links to Eclipse plugin development ) to use an enhanced API to become compatible out of the box with the Eclipse integration [2] .

The maven-scr-plugin should take advantage of these new APIs to allow seamless integration with Eclipse.

[0]: http://wiki.eclipse.org/M2E_plugin_execution_not_covered
[1]: http://wiki.eclipse.org/M2E/Extension_Development
[2]: http://wiki.eclipse.org/M2E_compatible_maven_plugins

Issue Links

• relates to: SLING-2423 Enhance the maven-scr-plugin to be compatible with recent Maven/Eclipse integrations

Sub-Tasks

• Ignore maven-scr-plugin executions in Eclipse: Closed
• Option to generate separate descriptor files: Closed
• Change default for generating descriptor files to generate single file for each component: Closed
• Use BuildContext for scanning changed files: Closed