Konrad Windszus created SLING-7720:
--------------------------------------
Summary: Conflicting lifecycle mapping bnd-maven-plugin:bnd-process
Key: SLING-7720
URL: https://issues.apache.org/jira/browse/SLING-7720
Project: Sling
Issue Type: Bug
Components: IDE
Affects Versions: Sling Eclipse IDE 1.2.2
Reporter: Konrad Windszus
Whenever a project is leveraging the {{biz.aQute.bnd:bnd-maven-plugin}} with
goal {{bnd-process}}, Eclipse emits the errors
{code}
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.
{code} and
{code}
Plugin execution not covered by lifecycle configuration:
biz.aQute.bnd:bnd-maven-plugin:4.0.0:bnd-process (execution: default, phase:
process-classes)
{code}
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-6112).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
