geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-4337) Upgrade to activeMQ 5.x
Date Wed, 04 Feb 2009 00:53:59 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Jencks closed GERONIMO-4337.
----------------------------------

    Resolution: Fixed

I think this is stable enough so we can use individual jira entries for any remaining problems.

> 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
>            Assignee: David Jencks
>             Fix For: 2.2
>
>         Attachments: geronimo-plugins.xml, plugins.svn.diff.zip, 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.


Mime
View raw message