JDK-4495771 : command line tools should all support -version
  • Type: Enhancement
  • Component: tools
  • Sub-Component: launcher
  • Affected Version: 1.4.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Won't Fix
  • OS: generic
  • CPU: generic
  • Submitted: 2001-08-23
  • Updated: 2013-04-30
  • Resolved: 2013-04-30
Related Reports
Relates :  
JDK-6415867 - ./extcheck -version gives a mis-leading output
Relates :  
JDK-4461214 - javac command line should have a "version" flag
Relates :  
JDK-6356148 - tools with -J should be consistently documented
Description
Name: bsC130419			Date: 08/23/2001


C:\jdk1.4\bin>java -version
java version "1.4.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta-b65)
Java HotSpot(TM) Client VM (build 1.4.0-beta-b65, mixed mode)

C:\jdk1.4\bin>

support the -version flag for all command line tools
starting with javac, rmic and other

This would greatly help when there is some path issue and a tool of a given
version is used instead of another one.

For my work, I need to have/workwith multiple JDKs/JREs as many other developers
in fact. Knowing which versions I'm using would sometimes help to
solve fast some strange behaviors.
(Review ID: 130566) 
======================================================================
###@###.### 2004-11-11 22:23:43 GMT
Comments
This issue has been around 12 years, most tools support -version flag and -J-version is always available except for those pure native tools, closing this as will not fix.
30-04-2013
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: dragon
14-06-2004
WORK AROUND Name: bsC130419 Date: 08/23/2001 none except digging into paths ====================================================================== This can be worked around using with a "-J-version" option to pass the "-version" option to the underlying Java command: myprompt>javac -J-version java version "1.4.2" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28) Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode) ###@###.### 2003-11-13
13-11-2003
EVALUATION Can do. Note this would hide or override any "-version" flag implemented in the code of the tool, so it will have to be explicitly enabled in the makefile. ###@###.### 2001-09-13 A reasonable request. As changes to command line options are involved, this will have to occur in a major release; committing to Tiger (1.5). ###@###.### 2002-11-14 No direct fix being considered for Tiger. Using "-J-version" should be an acceptable workaround; lowering severity accordingly. ###@###.### 2003-11-13
14-11-2002