[
https://issues.apache.org/activemq/browse/AMQ-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian Co resolved AMQ-1222.
----------------------------
Resolution: Fixed
Fix Version/s: 5.0.0
Patch applied! Thanks Tim!
Fixed in - http://svn.apache.org/viewvc?view=rev&rev=547575
BTW, more info for using the plugin here -
http://cwiki.apache.org/confluence/display/ACTIVEMQ/Maven2+ActiveMQ+Broker+Plugin
Let me know if you encounter any issues.
> Add option to fork broker from maven plugin
> -------------------------------------------
>
> Key: AMQ-1222
> URL: https://issues.apache.org/activemq/browse/AMQ-1222
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.0.0
> Reporter: Tim Morrow
> Assignee: Adrian Co
> Priority: Minor
> Fix For: 5.0.0
>
> Attachments: maven-plugin-fork-patch.txt
>
>
> Currently the maven plugin blocks after starting the broker. It would be
> nice if it could fork the broker to allow the Maven build to continue, for
> example to execute integration tests.
> See discussion here:
> http://www.nabble.com/Forking-activemq-with-maven-plugin-tf3527573s2354.html
> Patch attached which adds a "fork" option to the configuration. Default is
> false (current behavior). Example usage:
> {code:xml}
> ...
> <plugin>
> <groupId>org.apache.activemq.tooling</groupId>
> <artifactId>maven-activemq-plugin</artifactId>
> <executions>
> <execution>
> <phase>pre-integration-test</phase>
> <goals>
> <goal>run</goal>
> </goals>
> <configuration>
> <fork>true</fork>
> </configuration>
> </execution>
> </executions>
> </plugin>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
