2 Replies Latest reply on Feb 9, 2002 3:13 PM by gonso

    ANT W2K , HELP

    gonso

      Hello,

      I have my environment variables set properly:
      but as soon as I run ant I get that it is running
      java with no arguments.

      I created the build.xml with notepad, does it have
      something to do with this? sometimes notepad makes funny
      things with the xml-encoding.

      Please Help.
      Sincerely
      Ramón Talavera


      G:\tmp>ant
      Usage: java [-options] class [args...]
      (to execute a class)
      or java -jar [-options] jarfile [args...]
      (to execute a jar file)

      where options include:
      -hotspot to select the "hotspot" VM
      -server to select the "server" VM
      -classic to select the "classic" VM
      If present, the option to select the VM must be first.
      The default VM is -hotspot.

      -cp -classpath <directories and zip/jar files separated by ;>
      set search path for application classes and resources
      -D=
      set a system property
      -verbose[:class|gc|jni]
      enable verbose output
      -version print product version and exit
      -showversion print product version and continue
      -? -help print this help message
      -X print help on non-standard options

      --- ENVIRONMENT VARIABLES SET TO: -----
      SET CLASSPATH = G:\jdk1.3.1_01\include;G:\j2sdkee1.3\lib;G:\JBOSS\JBoss-2.4.4\lib;.\

      SET JAVA_HOME=G:\jdk1.3.1_01

      SET PATH=G:\jdk1.3.1_01\bin; ...

        • 1. Re: ANT W2K , HELP

          It hasn't got as far as build.xml

          The problem seems to be in ant.bat.
          Try adding some echos before it runs the java command,
          to see the actual command line.

          Have you defined ANT_HOME?

          Regards,
          Adrian

          • 2. Re: ANT W2K , HELP
            gonso

            It seems to be a v1.4.1 bug under W2K
            I have installed old v1.3 and it worked fine,
            so my environment variables were well setup.

            I am going to post the problem to the apache website.

            Thanks,
            Ramón Talavera