+ stderr & stdout logged to server/config/log/output.log and server/config/log/error.log.
+ A shutdown hook is registered with the VM to kill remaining jboss instances on shutdown.
+ If server does not respond to Shutdown request, the java.lang.Process is destroyed.
+ Supports nested java task arguments: jvmarg, arg, sysproperty
+ Core functionality is pure j2se code in test module; no dependencies on Ant or JBoss classes.
+ I have a schema for configuration with JBossXB, which could allow for shared configurations between the Ant testsuite and an eclipse plugin. However, Ant's xerces is incompatible with JbossXB.
+ Replace all start-jboss usage with server:start
+ Document usage
+ throw exception if server fails to stop instead of silently destroying process
+ possbily extend to controlling standalone tomcat instances?
The server tasks have been fully deployed to jboss-head/testsuite. Next week, I will be migrating this to jboss-4.0 so that we can have valid test runs for that branch as well.
Also, I moved these tasks to the test project so that they may be used by other projects like ejb3 (and potentially external ones, too).
Note:There still may be something wrong with the server shutdown (under cruisecontrol) which these tasks may mask. If the server fails to shutdown, it's process is destroyed. Really, if a server fails to shutdown, there should be a build failure
Related to the STDERR/STDOUT would it be possible to
allow the name of log/server.log to be overridden for each start/stop
and collected by the cruisecontrol process?
And the same for testsuite/output/log/test.log
That way, we can see more detail why a test failed without having to
try to reproduce it locally which might not always be possible?
Ant-JRunit already supports output for System.out and System.err for individual tests.
Maybe we should modify our XSL to support such thing.
Did we disable System.out and System.err for tests for any reason?
The AntRunner already captures system.out & system.err from testcases, doesn't it? I see it in the testuite/output/reports/TEST-*.xml files.
We are talking about system.out & err from the servers under test, not the test cases.
Ok, I'm going to merge these Ant tasks in to 4.0 as they seem to be holding up well enough in head.
If we wanted to use these tasks in our own Ant scripts, what JAR would contain the tasks?
Also, are the compatible with 4.0.0 ?
This is not included in the jboss dist. You will need to compile 4.0.x.
It will be under test/output/lib/jboss-test.jar. At the moment, it requires no other depedencies.