Bug 444539 - build-classpath and build-jar-repository return false positives
build-classpath and build-jar-repository return false positives
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: jpackage-utils (Show other bugs)
4.8
All Linux
low Severity low
: rc
: ---
Assigned To: Rodney Russ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-04-28 18:38 EDT by Deepak Bhole
Modified: 2012-06-20 09:18 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 09:18:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Deepak Bhole 2008-04-28 18:38:11 EDT
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):
1.7.3-1jpp.1.el4

How reproducible:
Always

Steps to Reproduce:
1. As root, create a fake jar with touch in /usr/share/java (touch
/usr/share/java/test-jar-1.0.jar)
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

Actual results:
#2 outputs /usr/share/java/test-jar-1.0.jar
#3 creates /tmp/[test-jar-1.0][file-does-not-exist].jar ->
/usr/share/java/test-jar-1.0.jar

Expected results:
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.

Additional info:
This issue appears to be fixed in RHEL-5.
Comment 2 Jiri Pallich 2012-06-20 09:18:45 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.