geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (GERONIMO-4337) Upgrade to activeMQ 5.x
Date Sat, 25 Oct 2008 06:35:46 GMT


David Jencks commented on GERONIMO-4337:

Sorry for the delay.

I dont think your svn.diff patch does anything useful at this point.  The versions for the
activemq and activeio jars are already specified in the plugins/activemq5/pom.xml in the <dependenciesManagement>
element, and at least for me building plugins/activemq5 fails on the geronimo-activemq5-core
module due to incompatible changes between activemq 4 and 5.  We can't change the rest of
the build to use activem5 until it actually works.  I think the next step would be to propose
some changes to the gbean classes so they compile against activemq 5.1.0.  Let me know if
I've missed some of your patches.

> Upgrade to activeMQ 5.x
> -----------------------
>                 Key: GERONIMO-4337
>                 URL:
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: ActiveMQ
>    Affects Versions: 2.2
>            Reporter: David Jencks
>             Fix For: 2.2
>         Attachments: geronimo-plugins.xml, svn.diff
> 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.

View raw message