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] Commented: (GERONIMO-4337) Upgrade to activeMQ 5.x
Date Wed, 15 Oct 2008 06:31:44 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639741#action_12639741
] 

David Jencks commented on GERONIMO-4337:
----------------------------------------

Hi John,

I'll keep my eyes out for the icla to arrive.

I thought that activemq 5 did not use activeio at all.
I don't understand what you mean by creating placeholders in .m2/repository.  Maven will create
any directories it needs when it needs them.
You should try to build from plugins/activemq5 and let maven figure out the order to build
the modules in.  Before updating the activemq versions I see:

[INFO]   Geronimo Plugins, ActiveMQ 5
[INFO]   Geronimo Plugins, ActiveMQ5 :: Management Interfaces
[INFO]   Geronimo Plugins, ActiveMQ5 :: Core
[INFO]   Geronimo Plugins, ActiveMQ5 :: Broker
[INFO]   Geronimo Plugins, ActiveMQ5 :: Resource Adapter Core
[INFO]   Geronimo Plugins, ActiveMQ5 :: Resource Adapter
[INFO]   Geronimo Plugins, ActiveMQ5 :: Portlets
[INFO]   Geronimo Plugins, ActiveMQ5 :: Console (Jetty)
[INFO]   Geronimo Plugins, ActiveMQ5 :: Console (Tomcat)

The error you get appears to refer to org.apache.geronimo.configs:activemq-ra and activemq-ra-4.1.2
which seems to indicate that some pom versions have not been updated to the proper values
for activemq 5 or geronimo activemq5.  If it is not clear how to proceed please attach a patch
from svn diff and I will investigate.

I would be surprised if the ActiveMQ5 Core module compiled successfully.

> 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.


Mime
View raw message