[jira] Commented: (AMQ-2105) Add support for rpm distribution

["Trevor Hemsley (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/AMQ-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58567#action_58567 ] 

Trevor Hemsley commented on AMQ-2105:
-------------------------------------

I tried to use the files attached to this JIRA today but three of the jars did not build correctly - these were smackx, geronimo-activation and geronimo-stax-api. All the supposed 'jar' files in the RPM that was created actually contain a HTML error message with a 302 - moved permanently status pointing to a different URL. Build was run on a Centos 5.4 i386 system and otherwise seems to complete ok.

In addition, when installed on Centos 5.4, the init script is linked to the wrong location - the files are installed under /opt/activemq but there is a dangling symlink created by the RPM installation that points to /usr/local/activemq/bin/activemq. The syntax of the adduser command in the post script is also wrong and tries to execute `adduser --system activemq` when on Centos5/RHEL5 this should say `adduser -r activemq`. These latter problems are easily fixed by editing the pre/post scripts and rebuilding the rpm.

Any idea how I get the correct smackx and geronimo jars to build? Am not a maven expert by any means!

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