Bug 986201

Summary: Unable to get effective pom when using dependencies defined in cxf parent bom
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Rostislav Svoboda <rsvoboda>
Component: Build, Maven RepositoryAssignee: Paul Gier <pgier>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.1CC: myarboro, nziakova, yyang
Target Milestone: ER4   
Target Release: EAP 6.1.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-16 20:27:58 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:

Description Rostislav Svoboda 2013-07-19 08:34:01 UTC
Issue related to CXF build - cxf parent and defined dependencies issue when receiving effective pom from test pom which imports all dependencies from cxf parent. 

dependencies.dependency.version and expression problems like this: 
  'dependencies.dependency.version' for org.jboss.spec.javax.servlet:${cxf.servlet-api-2.5.artifact}:jar is missing. @ line 75, column 13

Test pom file available on http://pastebin.test.redhat.com/154128

See http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Repository/job/eap-60-repository-maven-check-boms-for-effective-pom/78/testReport/cxf-parent-2.6.8-redhat-1/pom-BOM-test/cxf_parent_2_6_8_redhat_1_pom_BOM_test/

Error details available too in http://pastebin.test.redhat.com/154126

Comment 1 Rostislav Svoboda 2013-07-22 14:58:59 UTC
locker proposal because we are in 'blockers only' mode

Comment 2 Paul Gier 2013-07-23 20:31:36 UTC
This should be fixed with the latest build of apache cxf (2.6.8-redhat-3).
https://brewweb.devel.redhat.com/buildinfo?buildID=283080

Comment 3 Nikoleta Hlavickova 2013-08-05 13:30:54 UTC
Verified for EAP 6.1.1 ER4.
Note: since the build of apache cxf that fixes this issue there is new problem in maven repo - artifact is not named correctly - https://bugzilla.redhat.com/show_bug.cgi?id=993037