[ https://issues.jboss.org/browse/JBASMP-25?page=com.atlassian.jira.plugin.... ] James Perkins edited comment on JBASMP-25 at 10/23/12 1:45 PM: --------------------------------------------------------------- Comment Reference: https://github.com/jbossas/jboss-as-maven-plugin/issues/23#issuecomment-9... Ok, I thought that the run goal would not block, instead return control to maven once the server is started. If it is supposed to block then how should JBoss be shut down so that Maven would continue? BTW, {{StandaloneServer.isRunning()}} will return false if the server state is STARTING so the loop would exit rather than block if JBoss doesn't start almost immediately: {code} final ModelNode result = client.execute(Operations.createReadAttributeOperation(Operations.SERVER_STATE)); isRunning = Operations.successful(result) && !STARTING.equals(Operations.readResultAsString(result)) && !STOPPING.equals(Operations.readResultAsString(result)); {code} The scenario we are looking to support is: 1. Start JBoss from Maven, configuring datasources, queues etc. in the pre-integration-tests phase 2. Run a suite of integration tests using failsafe in the integration-tests phase 3. Shut down JBoss with the :shutdown command in the post-integration-tests phase 4. Failsure verifies the test results in the verify phase For this to work we would need the Run goal to fork JBoss once it's started rather than block. If it is supposed to block by design then can a configuration option be added to support forking? {code} <fork>true</fork> {code} was (Author: jamezp): Ok, I thought that the run goal would not block, instead return control to maven once the server is started. If it is supposed to block then how should JBoss be shut down so that Maven would continue? BTW, {{StandaloneServer.isRunning()}} will return false if the server state is STARTING so the loop would exit rather than block if JBoss doesn't start almost immediately: {code} final ModelNode result = client.execute(Operations.createReadAttributeOperation(Operations.SERVER_STATE)); isRunning = Operations.successful(result) && !STARTING.equals(Operations.readResultAsString(result)) && !STOPPING.equals(Operations.readResultAsString(result)); {code} The scenario we are looking to support is: 1. Start JBoss from Maven, configuring datasources, queues etc. in the pre-integration-tests phase 2. Run a suite of integration tests using failsafe in the integration-tests phase 3. Shut down JBoss with the :shutdown command in the post-integration-tests phase 4. Failsure verifies the test results in the verify phase For this to work we would need the Run goal to fork JBoss once it's started rather than block. If it is supposed to block by design then can a configuration option be added to support forking? {code} <fork>true</fork> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira