geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Charles (JIRA)" <>
Subject [jira] Commented: (GERONIMO-4337) Upgrade to activeMQ 5.x
Date Wed, 15 Oct 2008 06:13:44 GMT


John Charles commented on GERONIMO-4337:


I signed the icla and posted it from Australia.

I followed your instructions and downloaded everything including all the activemq5 plugin
modules. I firstly built geronimo from scratch. That worked fine. I then duplicated the local
playpen in preparation for ActiveMQ5.* inclusion.

I modified the following files under plugins on the local installation to ensure they validated
and performed a car:verify-no-dependency-change just to make sure things were structurally
- plugins\activemq5\pom.xml
- plugins\activemq5\activemq5-broker
- plugins\activemq5\activemq5-console-jetty
- plugins\activemq5\activemq5-console-tomcat
- plugins\activemq5\activemq5-ra
- plugins\activemq5\geronimo-activemq5
- plugins\activemq5\geronimo-activemq5-management
- plugins\activemq5\geronimo-activemq5-ra

I also bumped up the activemq-core, activemq-ra references to 5.1.0 and the activeio-core
to 3.1.0 as reflected in the ActiveMQ5.1 project. I can forward changes made to the pom files.

In addition to this I setup placeholder 2.2-SNAPSHOT version entries in my local .m2\repository
- .m2\repository\org\apache\geronimo\configs\activemq5-broker
- .m2\repository\org\apache\geronimo\configs\activemq5-ra
- .m2\repository\org\apache\geronimo\modules\geronimo-activemq5
- .m2\repository\org\apache\geronimo\modules\geronimo-activemq5-management
- .m2\repository\org\apache\geronimo\modules\geronimo-activemq5-ra
- .m2\repository\org\apache\geronimo\plugins\activemq5
- .m2\repository\org\apache\geronimo\plugins\activemq5-console-jetty
- .m2\repository\org\apache\geronimo\plugins\activemq5-console-tomcat
- .m2\repository\org\apache\geronimo\plugins\activemq5-portlets

I changed all version references to reflect ActiveMQ5.1 references for activemq-core, activemq-ra
and activeio-core namely 5.1.0, 5.1.0 and 3.1.0 respectively.

All good so far!! The next step involved systematically building (mvn install) on each of
the activemq5 plugin entries in the initial list.

The activemq5-broker built successfully however when I ran mvn install on the activemq5-console-jetty
entry I got the following problem:

[ERROR] The protocol for the JAR file's URL is not supported

java.lang.UnsupportedOperationException: Only local file jars are supported jar:file:/C:/Documents
and Settings/admin/.m2/repository/org/apache/geronimo/configs/activemq-ra/2.2-SNAPSHOT/!/rar/activemq-ra-4.1.2.jar






It looks like there was some discussion about issue from Jaceb Laskowski back in June 13 in
relation to changes made in GERONIMO-4093.

What was interesting was the activemq5-broker reported a similar problem but the build succeeded.

My goal at this stage is to incorporate a version of ActiveMQ5.* into Geronimo and then I
can wade into the other areas requiring modification.  I find it easier to wade into this
step by step given the overwhelming verbosity of maven output.

Let me know if I am on track and any insights on the above problem would be appreciated. I
have kept all build log files and can forward if required.


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