[SLING-7720] Conflicting lifecycle mapping bnd-maven-plugin:bnd-process

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: Sling Eclipse IDE 1.2.2
• Component/s: IDE
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 10/Jun/18 15:49
• Updated: 15/Jun/18 14:21
• Resolved: 15/Jun/18 14:21

Description

Whenever a project is leveraging the biz.aQute.bnd:bnd-maven-plugin with goal bnd-process, Eclipse emits the errors

Conflicting lifecycle mapping (plugin execution "biz.aQute.bnd:bnd-maven-plugin:4.0.0:bnd-process (execution: default, phase: process-classes)"). To enable full functionality, remove the conflicting mapping and run Maven->Update Project Configuration.

and

Plugin execution not covered by lifecycle configuration: biz.aQute.bnd:bnd-maven-plugin:4.0.0:bnd-process (execution: default, phase: process-classes)

This can e.g. be reproduced with the project at https://github.com/apache/sling-org-apache-sling-servlets-annotations-it.

The reasons for that seems to be that both the plugin itself as well as the Sling IDE provide a lifecycle mapping for that specific goal (SLING-6129).

Issue Links

• relates to: SLING-6129 Sling IDE: Support bnd-maven-plugin as well