Description of problem: Apparently "cglib" is the maven group id that this project uses upstream. We are currently including only "net.sf.cglib" in the maven dependencies map inside the file "/usr/share/maven-fragments/cglib", but "cglib" in the POM inside the file "/usr/share/maven-poms/JPP-cglib.pom". This generates some problems when building packages that use the upstream group id that are usually solved patching their POMs. Why are we using "net.sf.cglib"? If there is a reason for that can we at least add "cglib" as an alternative group id? Version-Release number of selected component (if applicable): cglib-2.2-9.fc17 How reproducible: Always. Steps to Reproduce: 1. Try to build using mvn-rpmbuild any package that requires cglib using "cglib:cglib" as the group id and artifact id. Actual results: The build fails. Expected results: The build should succeed. Additional info:
Created attachment 572466 [details] Proposed patch to add cglib:cglib to the dependencies map This patch ads cglib:cglib to the dependencies map. In fact it uses the %add_maven_depmap macro so that the gid:aid are taken from the POM. The "-a" option is used to add the previous "net.sf.cglib:cglib".
Fixed in Fedora 18+ in 2.2-11.