[
https://issues.apache.org/jira/browse/AMQ-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990559#comment-14990559
]
Timothy Bish commented on AMQ-5940:
-----------------------------------
We happily accept contributions so if you really want to see this included in a
future release go ahead and dive in and see what needs to be done there.
> Maven plugin stopped supporting many brokers run in the same Maven build
> ------------------------------------------------------------------------
>
> Key: AMQ-5940
> URL: https://issues.apache.org/jira/browse/AMQ-5940
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.12.0
> Reporter: Mateusz Nowakowski
>
> Maven ActiveMQ plugin 5.9.0 supported many ActiveMQ server being run in at
> the same time in one Maven build (especially when run Maven in parallel mode
> like -T1.5C).
> When migrated to ActiveMQ plugin 5.12.0:
> {code}
> Failed to execute goal
> org.apache.activemq.tooling:activemq-maven-plugin:5.12.0:run (startup
> activemq) on project cross-component: A local broker is already running "
> {code}
> It is because ActiveMQ Maven plugin keeps broker reference statically and
> checks it presence upon startup.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
