Red Hat Bugzilla – Bug 1015600
xmvn creating versioned jar dependencies
Last modified: 2013-10-07 08:05:54 EDT
Description of problem:
xmvn is creating versioned requires even if the pom fragment is not listing the package as a compat package. xmvn should be create unversioned requires even if the filename is versioned.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This can be seen in hadoop build having requires on 'mvn(commons-el:commons-el:1.0)'.
I just realized that this is caused by apache-commons-el being build when add_maven_depmap added <version> in <jpp> part of fragment as well and XMvn now believing this is a compat mapping.
I believe a possible workaround without need to rebuild every old package that might have versioned symlinks is warranted in this case. How about ignoring version tag in <jpp> part if the whole fragment is not a valid XML (and is therefore produced by old javapackages-tools that puts <version> everywhere).
This is not going to affect just commons-el but other packages as well
I cannot reproduce this.
Please include a (simple) reproducer.
This is a bug in individual packages and not with xmvn.