geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raj Saini <>
Subject Re: Configuring ActiveMQ with external file
Date Wed, 18 Mar 2009 05:32:34 GMT
Hi David,

I followed the following steps to build the Geronimo from trunk. 

1. Checkout the trunk
2. mvn install
3. mvn -Ptools geronimo:start

Geronimo started and I see activemq.xml file is not copied in var/activemq/conf folder. Web
console also do not provide any editing support. In fact there is no edit link there on running

I looked into the pom.xm and generated geronimo-plugin.xml and they do have the plugin-artifact
as you mentioned in your mail. 

Further I installed the created binary distribution (in ~/.m2/repository/org/apache/geronimo/assemblies
folder) to a separate folder and checked the geronimo-plugin.xml file in ${geronimo.home}/repository/org/apache/geronimo/configs/activemq-broker/2.2-SNAPSHOT/
folder and I did not find the two plugin-artifact lines to copy the activemq configuration.

Did I miss something?



From: David Jencks <>
Sent: Tuesday, 17 March, 2009 9:47:20 PM
Subject: Re: Configuring ActiveMQ with external file

In 2.2 we are using the "native" xbean-spring xml file to configure the activemq broker. 
By default it's installed into var/activemq/conf/activemq.xml by this info in the pom.xml/geronimo-plugin.xml:

                            <copy-file relative-to="server" dest-dir="var/activemq/conf">activemq.xml</copy-file>
                            <copy-file relative-to="server" dest-dir="var/activemq/template">activemq-template.xml</copy-file>

There's also some admin console support for editing this file which I think uses the activemq-template
file which is also installed.

In any case if you want to deal with editing this file individually on every server you can
just change it in place or if you want a more reproducible process you could copy the activemq-broker
maven project and build a plugin with your own plan.  Use an artifact-alias entry to make
your plugin replace ours.

hope this answers your question
david jencks


View raw message