Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-98

build.bat dos not process command line arguments correctly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.2.ALPHA1
    • 4.2.ALPHA1
    • System
    • None
    • Windows 2003

    • Workaround Exists
    • Hide

      Can run ant.bat directly, but this requires setting up the environment variables to point to the correct version of ant, which build.bat is supposed to do

      Show
      Can run ant.bat directly, but this requires setting up the environment variables to point to the correct version of ant, which build.bat is supposed to do
    • Low

      The batch script build.bat in the testsuite diredctory does not correctly deal long command lines, such as this required for testing: > build.bat -Djboss.dist=<dist location> -Dnode0=%MYTESTIP_1% -Dnode1=%MYTESTIP_2% -DudpGroup=239.11.12.13 tests

      Windows batch files throw out '=' signs when processing command line arguments. This the command line arguments above are:
      %1=-Djboss.dist
      %2=<dist location>
      %3=-Dnode0
      %4=%MYTESTIP_1%
      %5=-Dnode1
      %6=%MYTESTIP_2%
      %7=-DudpGroup
      %8=239.11.12.13
      %9=tests

      However, build.bat is written in such a way that it processes a maximum of 6 command line arguments. Thus, I can't run the testsuite with the command line above using build.bat. The same problem presumably applies to build.bat in the build directory.

      I have written a modification of build.bat which will handle command lines of any length, mimicking what the ant batch file does using the shift command. Will post this when JBoss Labs is available again.

        1. build.bat
          3 kB
        2. build.diff
          1 kB

            rachmato@redhat.com Richard Achmatowicz
            rachmato@redhat.com Richard Achmatowicz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: