Description of problem: Ivy 2.1.0 seems to have a bug resolving transitive dependencies, which causes it to look for the bogus version "working.name" Version-Release number of selected component (if applicable): apache-ivy.noarch 0:2.1.0-1.el6 How reproducible: 100% Steps to Reproduce: 1. rm -fr ~/.ivy2 && java -jar /usr/share/java/ivy.jar -dependency org.zanata zanata-cli 3.0.1 -warn -main org.zanata.client.ZanataClient Actual results: :::::::::::::::::::::::::::::::::::::::::::::: :: UNRESOLVED DEPENDENCIES :: :::::::::::::::::::::::::::::::::::::::::::::: :: org.jboss.resteasy#resteasy-jaxb-provider;working: not found :: org.jboss.resteasy#resteasy-multipart-provider;working: not found :::::::::::::::::::::::::::::::::::::::::::::: Expected results: Usage: zanata-cli [OPTION]... <command> [COMMANDOPTION]... Zanata Java command-line client ... Additional info: The Apache binaries for Ivy 2.1.0 fail with the same error: rm -fr ~/.ivy2 && java -jar ~/apps/apache-ivy-2.1.0/ivy-2.1.0.jar -warn -dependency org.zanata zanata-cli 3.0.1 -warn -main org.zanata.client.ZanataClient But 2.2.0 succeeds: rm -fr ~/.ivy2 && java -jar ~/apps/apache-ivy-2.2.0/ivy-2.2.0.jar -warn -dependency org.zanata zanata-cli 3.0.1 -warn -main org.zanata.client.ZanataClient Version 2.3.0 is also okay. NB: It's important to delete the Ivy cache before testing. Once Ivy 2.1.0 has corrupted the cache, Ivy 2.2.0 or 2.3.0 will fail with the same error.
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of EPEL please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.