Red Hat Bugzilla – Bug 965155
SY quickstart camel-soap-proxy maven-war-plugin with goal make-a-war in pom.xml triggers error on project import
Last modified: 2015-08-02 19:43:59 EDT
Description of problem:
SY quickstart camel-soap-proxy maven-war-plugin with goal make-a-war in pom.xml triggers error on project import in JBDS.
Steps to Reproduce:
1. Install SOA 6.0.0
2. in JBDS - File / Import / Maven / Existing Maven Projects
3. navigate to quickstarts/camel-soap-proxy
4. continue with Next button
5. see the error message
No marketplace entries found to handle Execution make-a-war, in /pom.xml in Eclipse. Please see Help for more information.
what fixed this issue is simply wrapping <plugins> with <pluginManagement>
Error message shown in JBDS Problems View:
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-war-plugin:2.1.1:war (execution: make-a-war, phase: compile) pom.xml /switchyard-quickstart-camel-soap-proxy line 96 Maven Project Build Lifecycle Mapping Problem
It should not make a difference to the Eclipse Maven tools whether or not the war plug-in is configured in plug-ins or plug-in management. And if you simply move the plugin to plugin management, you're not building the war, which is necessary to successfully test the quickstart.
The maven-war-plugin should be supported by the Eclipse Maven tooling, as should building two artifacts.
This should be pushed upstream to the Maven tools in Eclipse.