[
https://issues.apache.org/activemq/browse/AMQ-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59422#action_59422
]
James Casey commented on AMQ-2105:
----------------------------------
{quote}
* rpm creation should be automated
Maybe you can add activemq to SUSE build service to create RPMs for
several plattforms.
(see: http://de.opensuse.org/Build_Service)
Automatic creation of a daily snapshot based on svn-trunk would be a cool
idea.
{quote}
Yes, those were just some temp rpms We build it automatically on our Koji
(same as fedora) buildserver. Latest version at :
[https://koji.afroditi.hellasgrid.gr/koji/packageinfo?packageID=492]
{quote}
* ActiveMQ persistence data is currently located in /var/cache/activemq -
this looks not very
LSB compliant. Maybe /var/lib/activemq would be a better way
{quote}
Yes, probably. Now fixed.
{quote}
* /etc/activemq should only contain one single configuration
(all other activemq-*.xml configurations should be placed in
/usr/share/activemq/example/conf)
{quote}
This seems to be a problem with the upstream tarball creation. In the SVN repo
they're in a separate directory and get merged during the build process. I'll
submit a patch against the assembly descriptor to change this.
{quote}
* Basic configuration for the init-script should be moved to
/etc/default/activemq
{quote}
The init.d script loads from /etc/sysconfig/activemq which is the RHEL/fedora
equivalent of the debian /etc/default. I currently don't create a
/etc/sysconfig/activemq by default. I probably should.
{quote}
* ActiveMQ comes with the java wrapper:
/usr/share/activemq/bin/linux-x86-64/libwrapper.so
/usr/share/activemq/bin/linux-x86-64/wrapper
=> it seems that this is the main reason to have separate rpm-archives
for different platforms
=> in my opinion it would be a good idea to deliver activemq as a
"noarch" package by using
a init-script which do not need a binary helper.
(see also my implementation
https://issues.apache.org/activemq/browse/AMQ-2453, 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 using
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,...)
{quote}
Well the different platforms tend to have different rpms anyway since there are
differences in how the different platforms lay things out and what is provided
for init.d scripts (e.g. start-stop-daemon vs runuser and /etc/default vs
/etc/sysconfig. Also we we move to a 'real' rpm built for Fedora from source
it'll be x86_64 anyway since it must put the .so files for gcj into the package.
Tomcat5 on RHEL uses jakarata-commons-daemon for startup which also has a small
binary component. I know there are some licencing problems with JWS which
means we can't a newer version - I'll look at a patch to use
jakarta-commons-daemon instead and see if it's better.
{quote}
* ActiveMQ should not run as root-user as default
{quote}
the rpm creates an 'activemq' user and modifies the init.d to use it by default.
Thanks for the feedback, and any modifications you have to make it work on
non-RHEL rpm platforms would be welcome !
The latest rpm (5.3.2-3) is here :
[https://koji.afroditi.hellasgrid.gr/koji/buildinfo?buildID=623] and I'll
attach the tarball of the scripts to this ticket now.
> Add support for rpm distribution
> --------------------------------
>
> Key: AMQ-2105
> URL: https://issues.apache.org/activemq/browse/AMQ-2105
> 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:
> http://wiki.community.objectware.no/display/smidigtonull/RPM+Deployment+with+Java+Service+Wrapper
>
> 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.
