activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Cojocaru (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-4509) activemq-maven-plugin should have a stop goal
Date Thu, 16 Jan 2014 21:23:22 GMT

    [ https://issues.apache.org/jira/browse/AMQ-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873967#comment-13873967
] 

Alex Cojocaru commented on AMQ-4509:
------------------------------------

A fork of the ActiveMQ project in GitHub has support for stopping the ActiveMQ broker service
through the 'stop' goal:
https://github.com/alexcojocaru/activemq/tree/activemq-5.5.1.1

> activemq-maven-plugin should have a stop goal
> ---------------------------------------------
>
>                 Key: AMQ-4509
>                 URL: https://issues.apache.org/jira/browse/AMQ-4509
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: Maven 3.0.5, Java 6, Plugin configuration: <fork>true</fork>
>            Reporter: Tim Andersen
>            Priority: Minor
>              Labels: activemq-maven-plugin, maven-activemq-plugin
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The maven-activemq-plugin (aka activemq-maven-plugin) in a multi-module Maven project,
we would like to stop and start ActiveMQ for each module where it is needed (a "stop" and
"start" goal, rather than a "run" goal with a shutdown hook). We cannot run an individual
module of our multi-module project because we can only start ActiveMQ once for our aggregate
pom.xml. This approach would also resolve AMQ-1628 in a different way than was suggested.
The approach we are suggesting is similar to how the cargo plugin handles tomcat.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message