[jboss-jira] [JBoss JIRA] (JBASMP-25) Don't kill maven process after run goal cancellation

[James Perkins (JIRA)]

    [ https://issues.jboss.org/browse/JBASMP-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728689#comment-12728689 ] 

James Perkins commented on JBASMP-25:
-------------------------------------

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}
                
> Don't kill maven process after run goal cancellation
> ----------------------------------------------------
>
>                 Key: JBASMP-25
>                 URL: https://issues.jboss.org/browse/JBASMP-25
>             Project: JBoss AS Maven Plugins
>          Issue Type: Enhancement
>            Reporter: James Perkins
>            Assignee: James Perkins
>
> Is it possible to reopen this issue? The {{jboss-as:run}} goal does not help when the deployment is to be used in the same Maven build, since the goal tends to block subsequent goals. For example, using this goal in the {{pre-integration-test}} phase, prevents the maven-failsafe-plugin from executing integration tests.
> Is it possible to introduce goals atleast to start and stop standalone JBoss 7 instances, so that a Maven CI build could manage the lifecyle of the instance ?

--
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