geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Charles (JIRA)" <>
Subject [jira] Updated: (GERONIMO-4337) Upgrade to activeMQ 5.x
Date Tue, 21 Oct 2008 09:51:44 GMT


John Charles updated GERONIMO-4337:

    Attachment: geronimo-plugins.xml

I have built the activemq5 plugin. I made some changes to various pom.xml files as reflected
in the attachment.

The next step is to incorporate ActiveMQ5 references in the various geronimo assemblies. I
assume this is done via a maven repository hosting the geronimo-plugins.xml file located at{version}. I attached my guess at the reference
changes required using a new version number of 2.2.1-SNAPSHOT.

Let me know if I am on the right track. If so, I guess I would need to wait until the online
assembly configuration file geronimo-plugins.xml is ready.

John Charles

> 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