Bug 835574

Summary: When setting up workspace, the dynamically generated classes are not added to classpath
Product: [Other] RHQ Project Reporter: Jirka Kremser <jkremser>
Component: Build SystemAssignee: Jirka Kremser <jkremser>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: hrupp
Target Milestone: ---   
Target Release: RHQ 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-01 06:06:08 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Jirka Kremser 2012-06-26 10:05:25 EDT
Description of problem:
There are few modules, where some Java classes are generated during mvn build process. Unfortunately, IDE does not know about them and reports many errors. The generated sources come from xjc (xml schema to Java classes), antlr (Parser Generator) and GWT (Messages, Async interfaces).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.pull the project sources using git
2.import the project as a maven project
3.wait for errors
Actual results:
5202 errors in Eclipse

Expected results:
0 errors

Additional info:
Comment 1 Jirka Kremser 2012-06-26 12:05:50 EDT

git log master
time:    Tue Jun 26 18:02:25 2012 +0200
commit:  2dc5e65abef4476d0b2a6247d258488688232888
author:  Jirka Kremser - jkremser@redhat.com
message: [BZ 835574 - When setting up workspace, the dynamically generated classes are not added to classpath] Solved using the org.codehaus.mojo:build-helper-maven-plugin. It adds the generated sources. NOTE: the mvn "process-resources" should be checked in the IDE Maven settings
Comment 2 Heiko W. Rupp 2013-09-01 06:06:08 EDT
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.