[
https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639840#action_12639840
]
Donald Woods commented on GERONIMO-4337:
----------------------------------------
John, I just made a small update to the activemq5/pom.xml in Rev704910 to
upgrade to the AMQ 5.1.0 artifacts and to keep the console modules from
building. Feel free to start creating patches and attaching them to this JIRA
and we'll get them applied ASAP, so you can keep making progress. Thanks!
> Upgrade to activeMQ 5.x
> -----------------------
>
> Key: GERONIMO-4337
> URL: https://issues.apache.org/jira/browse/GERONIMO-4337
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.2
> Reporter: David Jencks
> Fix For: 2.2
>
>
> Upgrade activemq support to 5.x. A few steps along the way:
> - create an activemq5 work area under plugins
> - move the specification of amq version from the root pom dependency
> management to the activemq and activemq5 plugins.
> - keep only the broker gbean
> - use an activemq configuration file in var/activemq, referenced by the
> broker gbean
> - update dependencies to latest activemq
> - figure out how much of the current jms portlet functionality can be
> reasonably kept. From discussions with Hiram I think that trying to
> reconfigure the broker while its running is a very bad idea and we should
> just drop the parts of the console that try to do this.
> - investigate how to run the amq console in geronimo, preferably as portlets
> inside the g. admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
