-
Bug
-
Resolution: Done
-
Major
-
JBossAS-4.2.0.CR1
-
None
-
Low
-
Workaround Exists
-
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.
- blocks
-
JBPAPP-98 build.bat dos not process command line arguments correctly
- Closed