Bug 154704 - Java does not seem to build CLASSPATH properly
Java does not seem to build CLASSPATH properly
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: java-1.4.2-gcj-compat (Show other bugs)
rawhide
powerpc Linux
medium Severity medium
: ---
: ---
Assigned To: Thomas Fitzsimmons
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-13 12:46 EDT by W. Michael Petullo
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-04-15 15:25:29 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 W. Michael Petullo 2005-04-13 12:46:51 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.7.6) Gecko/20050322 Epiphany/1.5.8

Description of problem:
The java command does not seem to build Java's CLASSPATH properly.  If I add statement to the script that prints the contents of CLASSPATH right before gij is executed, I get:

/usr/share/java/libgcj-java version 1.4.2.jar

There are two problems with this:

1.  This path is not correct.

2.  If I execute gij with CLASSPATH not set, gij will search "." by default.  However, if I execute java with CLASSPATH not set, java will build a CLASSPATH that does not include ".".  As a result, java will not search "." by default.

Version-Release number of selected component (if applicable):
java-1.4.2-gcj-compat-1.4.2.0-40jpp_14rh

How reproducible:
Always

Steps to Reproduce:
1.  Select a program that uses classes in ".".

2.  Execute the program using gij.

3.  Execute the program using java.
  

Actual Results:  Step 2 succeeds.  Step 3 fails because "." is not searched for classes.

Expected Results:  Steps 2 and 3 should succeed.

Additional info:
Comment 1 Thomas Fitzsimmons 2005-04-15 15:25:29 EDT
Fixed in Rawhide.  Closing.

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