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

Tue Feb 12 03:00:57 EST 2013

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

Martin Gustafsson commented on JBASMP-25:
-----------------------------------------

Good question. 

I should say that before the scenario above is performed we are adding our own modules to support jsr289 and updating the javaee.api module to include the SIP Servlet API etc to the JBoss/EAP. We do this by using several maven plugins and the result is an extended EAP ready to go.

Do you think we can do the same with Arquillian?

> 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