From: Pierre Delisle <Pierre.Delisle_at_Sun.COM>
Date: Mon, 22 Aug 2005 13:22:03 -0700

On a windows XP platform, I installed promoted build 14,
unjar'ed the jar file.

When running "ant -f setup.xml", I get the following:

create.domain.windows:
     [exec] java.lang.UnsupportedClassVersionError: com/sun/enterprise/cli/frame
work/CLIMain (Unsupported major.minor version 49.0)
     [exec] at java.lang.ClassLoader.defineClass0(Native Method)
     [exec] at java.lang.ClassLoader.defineClass(ClassLoader.java:539)


This is probably because 1.4 is picked up instead of J2SE 5.0.
However, my path has J2SE 5.0 in it.

If I run "java -version" prior to running ant, I get:

  D:\glassfish-b14>java -version
  java version "1.5.0_01"
  Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08)
  Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode)

And if I add the following in the ant script prior to the 'exec' that
fails:

    <exec executable="java" failonerror="true">
        <arg line="-version" />
    </exec>

I get:

     [exec] java version "1.5.0_01"
     [exec] Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08)
     [exec] Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode)

So it looks like J2SE 5.0 should be picked up, but it isn't.

Also, if I echo the value of the java.home in "get.java.home",
I get the following:

D:\glassfish-b14>ant -f setup.xml get.java.home
Buildfile: setup.xml

get.java.home:
     [echo] java.home: d:\jdk1.5.0_01\jre


Any idea why a jdk 1.4 keeps being invoked for the exec while
everything seems to properly point to J2SE 5.0?

Thanks,

    -- Pierre