Bug 869638

Summary: Seam2.3: TAG-16 Groovybooking example
Product: [Retired] JBoss Enterprise WFK Platform 2 Reporter: Marek Schmidt <maschmid>
Component: Examples, SeamAssignee: Marek Novotny <mnovotny>
Status: CLOSED WONTFIX QA Contact: Marek Schmidt <maschmid>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.1.0CC: bsutter, rruss, snagarwa
Target Milestone: CR1   
Target Release: 2.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: Seam2.3 seam-example
Fixed In Version: Doc Type: Known Issue
Doc Text:
Seam groovybooking example uses the maven-antrun-plugin, which JBDS cannot import automatically. As a consequence, Seam groovybooking cannot be built automatically in JBDS. As a workaround, use Maven (mvn clean package) to build the groovybooking example.
 Story Points: ---
Clone Of: 830202
: 947468 (view as bug list) Environment:
Last Closed: 2013-03-20 09:28:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 947468    

Description Marek Schmidt 2012-10-24 13:05:24 UTC 
The Seam2.3 groovybooking example import into JBDS with errors. Ignoring the errors does *not* lead to a working example in JBDS, despite the comments in the original bz, as the groovy sources will not be compiled in JBDS.

(note that the example still can be built with Maven)

+++ This bug was initially created as a clone of Bug #830202 +++

Following errors happen in groovybooking example when imported to JBDS (ignoring missing Maven artifacts):


Description	Resource	Path	Location	Type
Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:build-helper-maven-plugin:1.5-redhat-1:add-test-source (execution: add-test-source, phase: generate-test-sources)	pom.xml	/groovybooking-tests	line 84	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:build-helper-maven-plugin:1.5-redhat-1:add-source (execution: add-source, phase: generate-sources)	pom.xml	/groovybooking-web	line 200	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.codehaus.gmaven:gmaven-plugin:1.4:testCompile (execution: default, phase: test-compile)	pom.xml	/groovybooking-web	line 133	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.codehaus.gmaven:gmaven-plugin:1.4:generateTestStubs (execution: default, phase: generate-test-sources)	pom.xml	/groovybooking-web	line 133	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.codehaus.gmaven:gmaven-plugin:1.4:generateStubs (execution: default, phase: generate-sources)	pom.xml	/groovybooking-web	line 133	Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: org.codehaus.gmaven:gmaven-plugin:1.4:compile (execution: default, phase: compile)	pom.xml	/groovybooking-web	line 133	Maven Project Build Lifecycle Mapping Problem

--- Additional comment from mnovotny on 2012-06-15 05:45:23 EDT ---

These errors are related to M2e plugin in Eclipse/JBDS and they are not really important. It says only that M2e plugin doesn't know how to handle some maven plugins used in example's pom.xml file.

More information at http://wiki.eclipse.org/M2E_plugin_execution_not_covered

As summary - you have got two options:
1. download/install plugin for haddling the affected maven plugin lifecycle
see section "m2e maven plugin coverage status"  on referenced above wiki page URL
2. Ignore it by adding of plugin configuration for org.eclipse.m2e:lifecycle-mapping:1.0.0

I don't like any from these 2 solutions and even it shows error it is build-able.
I am not considering this as a bug, just a technical note could be added for this particular case.
Comment 1 Marek Novotny 2012-11-06 12:33:44 UTC 
moving to next release
Comment 2 Marek Novotny 2013-03-19 10:14:34 UTC 
added m2e lifecycle handling in https://source.jboss.org/changelog/Seam?cs=15452

Even now it shows different errors, The import org.jboss.seam.example.groovy.model.User cannot be resolved	in AuthenticatorAction.java and in ChangePasswordAction.java due m2e lifecycle is ignoring execution of maven-antrun-plugin and doesn't generate classes from groovy scripts.

As maven-antrun-plugin has got no m2e connector, I would say it is not fixable.
Comment 3 Marek Novotny 2013-03-20 09:28:43 UTC 
closing as won't fix. Look for https://bugzilla.redhat.com/show_bug.cgi?id=869638#c2 as an explanation.
Comment 4 Sneha 2013-03-21 09:12:43 UTC 
Doc Text updated.