Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Abandoned
-
5.2.0
-
None
-
None
-
linux, rpm-based
Description
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.