Good point. You can find out with twiddle:
JBOSS_HOME\bin>twiddle get "jboss.system:type=Server" BuildDate BuildJVM BuildOS BuildDate=March 7 2009 BuildJVM=1.5.0_16-b02(Sun Microsystems Inc.) BuildOS=Windows XP(x86,5.1)
Two ways I can think of.
1) Visual inspection: the jdk6 variant has jbossws*.jar files in lib/endorsed.
2) Via the log file: the jdk6 variant reports the version as:
12:55:56,005 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812042120)
while the jdk5 variant reports the version as:
15:33:59,995 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812041714)
Note the slightly different build dates.
I like to have both variants handy, so after I unpack them I rename the base directory to add the jdk version, Examples: jboss-5.0.0.GA-jdk5 and jboss-5.0.0.GA-jdk6.
Running twiddle on a Java 6 build is reported like this:
BuildDate=February 23 2009 BuildJVM=11.0-b16(Sun Microsystems Inc.) BuildOS=Linux(i386,2.6.9-67.0.1.ELsmp)
Java 11!!!! That must be the best version of Java ever!
Kidding, there would appear to be discrepancy between the java versions returned by running "java -version".
java version "1.5.0_07" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03) Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode, sharing)
java version "1.6.0_12" Java(TM) SE Runtime Environment (build 1.6.0_12-b04) Java HotSpot(TM) Client VM (build 11.2-b01, mixed mode, sharing)
You'll note that the build number for the client VM differs between 5 and 6. On 5 in infers the java versions and on 6 it does not. This behaviour occurs on both windows and linux.
Maybe we need a "BuildRuntime" variable as well???