Bug 965155 - SY quickstart camel-soap-proxy maven-war-plugin with goal make-a-war in pom.xml triggers error on project import
Summary: SY quickstart camel-soap-proxy maven-war-plugin with goal make-a-war in pom.x...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Examples, SwitchYard
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Brian Fitzpatrick
QA Contact: Jiri Sedlacek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-20 14:45 UTC by ppecka
Modified: 2015-08-02 23:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-09 19:24:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description ppecka 2013-05-20 14:45:38 UTC
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

Actual results:
No marketplace entries found to handle Execution make-a-war, in /pom.xml in Eclipse.  Please see Help for more information.

Expected results:


Additional info:
what fixed this issue is simply wrapping <plugins> with <pluginManagement>
 <build>
     <finalName>${project.artifactId}</finalName>
     <pluginManagement>
        <plugins>
            <plugin></plugin>
            <plugin></plugin>
        </plugins>
     </pluginManagement>
 </build>

Comment 1 ppecka 2013-05-21 09:37:49 UTC
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

Comment 2 Brian Fitzpatrick 2013-09-09 19:24:10 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.