|
Quick Lists
|
|
Bug ID:
|
6400872
|
|
Votes
|
0
|
|
Synopsis
|
REGRESSION: Java Compiler cannot find jar files referenced by other
|
|
Category
|
java:compiler
|
|
Reported Against
|
|
|
Release Fixed
|
mustang(b85)
|
|
State
|
10-Fix Delivered,
Verified,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
6446657
,
6456960
,
6485027
,
6206485
|
|
Submit Date
|
20-MAR-2006
|
|
Description
|
A DESCRIPTION OF THE REGRESSION :
I have tried the exact same compile command on Java 1.4, Java 1.5, and Java 1.6 beta. Compiling with 1.4 and 1.5 is fine. When I execute the command against 1.6 compiler I get:
---------------------------------------------------------------------------------------------------------------------------------
error: error reading lib\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\commons-logging-api-1.0.2.jar; The system cannot find the path specified
error: error reading lib\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\commons-collections-api-1.0.2.jar; The system cannot find the path specified
error: error reading lib\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\commons-fileupload-api-1.0.2.jar; The system cannot find the path specified
---------------------------------------------------------------------------------------------------------------------------------
I recieve many of these messages, and some are duplicated. The jar files in question are in the lib directory and as stated earlier are found by 1.4 and 1.5. Looking at the MANIFEST of one of my jars, it references others using './jarname.jar', and even referenced it's self. I removed the self reference and the './' from all the other jar files but still did not work. Several of the jars point to each other in the MANAFESTS Class-Path element.
REPRODUCIBLE TESTCASE OR STEPS TO REPRODUCE:
Multiple jar files, each with a Class-Path in the MANIFEST.MF. The jar files point to each other, referencing each other as ./jarname.jar. Use these jar files in the -classpath of the compiler.
RELEASE LAST WORKED:
5.0 Update 4
RELEASE TEST FAILS:
mustang-beta
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
I expected the compile to be successful as it was using both 1.4 and 1.5
ACTUAL -
C:\WORKSPACE>"%JAVA_HOME%\bin\javac" -classpath lib/core.jar;lib/beans.jar;C:\jboss\server\default\lib\jboss-j2ee.jar -d
/bin/classes -sourcepath /src src/XMLImport.java
error: error reading lib\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
\beans.jar; The system cannot find the path specified
error: error reading lib\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
\apps.jar; The system cannot find the path specified
error: error reading lib\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
\inbound.jar; The system cannot find the path specified
error: error reading lib\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
\commons-collections-2.1.jar; Filename too long
error: error reading lib\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
\commons-logging-api-1.0.2.jar; Filename too long
error: error reading lib\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.
\commons-fileupload-1.0.jar; Filename too long
...
Posted Date : 2006-03-20 14:57:49.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
Reproduced test case on Linux
Posted Date : 2006-05-02 19:31:22.0
The check whether a file was already in the path did not use the canonical path of the file.
The fix is to keep a cache of the canonical values of the entries on the path, and to check the canonical value of any new entries against that list.
Posted Date : 2006-05-02 19:59:29.0
|
|
Comments
|
Submitted On 18-JUN-2007
kitsue
Have been using 5.0 Update 8 with no problems, just installed JDK 5.0 Update 12 and received this exact problem.
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |