You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2012/10/07 14:46:02 UTC

[jira] [Resolved] (AMQ-1628) actitvemq-maven-plugin should shutdown after execution of the maven module (with fork flag set to true)

     [ https://issues.apache.org/jira/browse/AMQ-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved AMQ-1628.
------------------------------

    Resolution: Won't Fix
      Assignee: Claus Ibsen

This is not the intend of this plugin.
                
> actitvemq-maven-plugin should shutdown after execution of the maven module (with fork flag set to true)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1628
>                 URL: https://issues.apache.org/jira/browse/AMQ-1628
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 5.0.0
>            Reporter: Dirk Pitt
>            Assignee: Claus Ibsen
>             Fix For: NEEDS_REVIEWED
>
>
> Hallo,
> in our project we are trying to use the activemq-maven-plugin in unit testing....
> Our Maven project consist of several modules, if we are using the activemq plugin in one of this modules, it stays up (with fork set true) for the execution of the other  maven module.
> Better would be I guess, activemq plugin should listen the lifecycles of the maven module (sub project) and shutdown when the module execution completes
> Otherwise another module, further down in the hierharchy that doesn't know the existance of the other unit test may start the activemq plugin and cause exceptions

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