JDK-6510337 : javaw launcher should also support class-path wildcards
  • Type: Bug
  • Component: tools
  • Sub-Component: launcher
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_2000,windows_xp
  • CPU: x86
  • Submitted: 2007-01-05
  • Updated: 2017-05-16
  • Resolved: 2011-07-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7
6u2Fixed 7 b09Fixed
Related Reports
Duplicate :  
JDK-6519476 - -cp option in java.exe and javaw.exe is handled differently for wildcards(*)
Relates :  
JDK-6268383 - Class-path wildcards, jplan feature 082
Description
The Windows specific java launcher 'javaw' does not have class path expansion enabled. This is a bug since it should work according to the J2SE 6 docs at http://java.sun.com/javase/6/docs/technotes/tools/windows/java.html. This problem has also been reported at http://forum.java.sun.com/thread.jspa?threadID=5118123. The fix is to copy the expression "OTHER_CPPFLAGS += -DEXPAND_CLASSPATH_WILDCARDS" from j2se/make/java/main/java/Makefile to j2se/make/java/main/javaw/Makefile.
Comments
EVALUATION I agree that java and javaw should treat wildcards consistently. The proposed fix looks right.
05-01-2007
WORK AROUND Use the java.exe instead of the javaw.exe launcher in JDK/JRE 6 on Windows.
05-01-2007