| Summary: | xmvn creating versioned jar dependencies | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Robert Rati <rrati> |
| Component: | xmvn | Assignee: | Mikolaj Izdebski <mizdebsk> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | mizdebsk, msrb, rrati, sochotni, tradej |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-10-07 12:05:54 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: | |
|
Description
Robert Rati
2013-10-04 15:04:08 UTC
This can be seen in hadoop build[1] 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 [1] http://koji.fedoraproject.org/koji/rpminfo?rpmID=4457357 I cannot reproduce this. Please include a (simple) reproducer. This is a bug in individual packages and not with xmvn. |