Description of problem:
build-classpath and build-jar-repository in RHEL4 return bad matches in certain
cases where the supplied argument jar does not exist.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. As root, create a fake jar with touch in /usr/share/java (touch
2. Run build-classpath test-jar-1.0/file-does-not-exist
3. Run build-jar-repository /tmp test-jar-1.0/file-does-not-exist
#2 outputs /usr/share/java/test-jar-1.0.jar
#3 creates /tmp/[test-jar-1.0][file-does-not-exist].jar ->
Both, #2 and #3 should say that the file was not found, instead of thinking
/usr/share/java/test-jar-1.0.jar is the correct jar.
This issue appears to be fixed in RHEL-5.
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life.
Please See https://access.redhat.com/support/policy/updates/errata/
If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.