-
Bug
-
Resolution: Not an Issue
-
P3
-
None
-
1.3.0
-
x86
-
windows_nt
Name: krT82822 Date: 11/06/99
11/6/99 eval1127@eng -- This bizarre problem is reproducible on NT 4.0 SP 4 with even the RA (1.3.0 build I) release of kestrel (1.3). Does not occur on Solaris.
Briefly thought "con.jar" was perhaps an obscure jar somewhere in the win32 (non-JDK) dirs or such.
Had we reserved "con.jar" as a special filename to mean "write to console"? Tried alt. filenames such as "con.txt" with no change in behavior.
Removed the "M" flag, and there was no change.
Since "con" has special meaning on win32 (old DOS-ism), does something weird happen in the cmd-line parsing if "con.anything" is passed? Dunno. FIling bug,
since I can't con.jar (i.e., conjure) up any other ideas.
-----------
[Filed against:] java version "1.2.2" [but still present in kestrel-RA]
Classic VM (build JDK-1.2.2-W, native threads, symcjit)
When we specify the jar file name as "con.jar", instead of creating the jar
file it will print some ascii chars, some thing like this (every time the first
2 chars are the same.
"PK♥ FQZ' ► ♦ ConfigTest.class?- ?SmO+P?~.←??E?+". It happens Only
for "con.jar" filename it happens. The command line arguments are as follows:
jar cfM con.jar *.class
(Review ID: 97553)
======================================================================