activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-4510) activemq-maven-plugin should optionally not fail if already started
Date Mon, 06 May 2013 20:34:16 GMT

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

Timothy Bish updated AMQ-4510:
------------------------------

      Priority: Minor  (was: Major)
    Issue Type: New Feature  (was: Bug)
    
> activemq-maven-plugin should optionally not fail if already started
> -------------------------------------------------------------------
>
>                 Key: AMQ-4510
>                 URL: https://issues.apache.org/jira/browse/AMQ-4510
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: Maven 3.0.5, Java 6, Plugin config: <fork>true</fork>
>            Reporter: Tim Andersen
>            Priority: Minor
>              Labels: activemq-maven-plugin, maven-activemq-plugin
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Using the maven-activemq-plugin (aka activemq-maven-plugin) in a multi-module build the
plugin throws an exception and fails the build if it was started by another module in the
same build. This is a problem because there is no way to stop the broker from the previous
module, and in a multi-module build the broker does not stop until all modules in the build
reactor are finished. Because of this problem, a single module cannot be run independently.
An optional configuration flag <continueIfAlreadyRunning/> would address this problem.
See related AMQ-4509.

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

Mime
View raw message