[
http://jira.jboss.com/jira/browse/JBAS-4243?page=all ]
Dimitris Andreadis closed JBAS-4243.
------------------------------------
Fix Version/s: JBossAS-5.0.0.Beta2
Resolution: Done
Assignee: Dimitris Andreadis
Ok, I've applied the change on both build/testsuite build.bat for Branch_4_2 and
HEAD.
build.bat does not process command line arguments correctly
-----------------------------------------------------------
Key: JBAS-4243
URL:
http://jira.jboss.com/jira/browse/JBAS-4243
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-4.2.0.CR1
Environment: Windows 2003
Reporter: Richard Achmatowicz
Assigned To: Dimitris Andreadis
Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira