[arquillian-issues] [JBoss JIRA] Issue Comment Edited: (ARQ-282) DeployableContainer.stop(Context) never called

[Aslak Knutsen (JIRA)]

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

Aslak Knutsen edited comment on ARQ-282 at 5/30/11 1:47 PM:
------------------------------------------------------------

Maven-Surefire runs test as individual tests in the default JUnitProvider reusing the same notifier but never calls testRunFinished. As far as I can find, there is no way to figure out what is the last test to run so we can shutdown using this Provider.

JUnit47Provider does call testRunFinished, but only way to configure it is to set <parallel> to something, e.g. none. (but will validate that forkmode is not forkNever).



      was (Author: aslak):
    Maven-Surefire runs test as individual tests in the default JUnitProvider reusing the same notifier but never calls testRunFinished. As far as I can find, there is no way to figure out what is the last test to run so we can shutdown using this Provider.

JUnit47Provider does call testRunFinished, but only way to configure it is to set parallel to something, e.g. none. (but will validate that forkmode is not forkNever).


  
> DeployableContainer.stop(Context) never called
> ----------------------------------------------
>
>                 Key: ARQ-282
>                 URL: https://issues.jboss.org/browse/ARQ-282
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Deployable Containers SPI
>    Affects Versions: 1.0.0.Alpha5
>            Reporter: Thomas Diesler
>             Fix For: 1.0.0.CR1
>
>
> This is true for the embedded and remote OSGi containers

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira