activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Schöchlin (JIRA) <>
Subject [jira] Commented: (AMQ-2105) Add support for rpm distribution
Date Sun, 16 May 2010 16:46:13 GMT


Marc Schöchlin commented on AMQ-2105:


thank you for wrining the specfile - i take a quick view at your RPM (just inspected by using

Some ideas/hints from a sysadmin's view:

- rpm creation should be automated
  Maybe you can add activemq to SUSE build service to create RPMs for several plattforms.
  Automatic creation of a daily snapshot based on svn-trunk would be a cool idea.
- ActiveMQ persistence data is currently located in /var/cache/activemq  - this looks not
  LSB compliant. Maybe /var/lib/activemq would be a better way
- /etc/activemq should only contain one single configuration
  (all other activemq-*.xml configurations should be placed in /usr/share/activemq/example/conf)
- Basic configuration for the init-script should be moved to
- ActiveMQ comes with the java wrapper:
  => it seems that this is the main reason to have separate rpm-archives for different
  => in my opinion it would be a good idea to deliver activemq as a "noarch" package by
     a init-script which do not need a binary helper.
     (see also my implementation, unluckily
i got no feedback
     what is needed to get it in activemq-svntrunk) 
  => in my opinion it would be a good idea to deliver activemq as a "noarch" package by
     a init-script which do not need a binary helper.
     (noarch packages can i.e. be used on linux-x86/x86_64/s390/arm/.. and also on systems
which support rpm like aix/pseries,...)
- ActiveMQ should not run as root-user as default

I'm also interested in having distribution packages of activemq - if you like i can contribute
to the specfiles....


> Add support for rpm distribution
> --------------------------------
>                 Key: AMQ-2105
>                 URL:
>             Project: ActiveMQ
>          Issue Type: New Feature
>    Affects Versions: 5.2.0
>         Environment: linux, rpm-based
>            Reporter: Erik Drolshammer
>         Attachments: activemq-rpm.tar.bz2, activemq-rpm_standalone-project.tar.bz2
> Todo: 
> * Create separate rpm maven project 
> * move config, scripts, documentation from the jar project 
> 14:57 < Sherriff> Have you thought about distribution with for example rpm? 
> 14:58 < Sherriff> gtully: It seems to be working a lot better without systemUsage
and destinationPolicy defined. Thanks alot :) 
> 14:58 < rajdavies> Sherriff: yeah - would be a good idea
> 14:59 < Sherriff> rajdavies: Do you use Maven2 to build it now? 
> 14:59 < rajdavies> Sherriff: yep
> 15:00 < Sherriff> Cool. 
> 15:00 < Sherriff> If you would like I can set up an rpm-project based on appassembler-m-p
and unix-m-p. 
> 15:01 < Sherriff> for you. 
> 15:01 < rajdavies> Sherriff: that would be awesome!
> 15:02 < Sherriff> It use Java Service Wrapper and some (a bit outdated doc) can
be found here:

> 15:02 < Sherriff> The project setup would then be 1. jar-project and 2. rpm-project.
> 15:03 < Sherriff> 2. Would contain config file, readmes, etc. and the start/stop
scripts are generated by appassembler. 
> I can probably do most of the work since I already have working rpm setup that I use
for other projects. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message