Automated Java Deployments With Rpm
by Martin Jackson on Oct 28, 2011
- 5,883 views
Using the RPM Maven Plugin to package Java Artefacts for fun and profit.
Using the RPM Maven Plugin to package Java Artefacts for fun and profit.
Accessibility
Tags
More...Upload Details
Uploaded via SlideShare as Adobe PDF
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 20
- Downloads
- 83
- Comments
- 4
- Embed Views
- Views on SlideShare
- 5,488
- Total Views
- 5,883

The initial problem was because the environment was not externalized and they were shipped with just the development parameters, deployments were problematic i.e. we could not guarantee that the application would work consistently without puppet being running twice. 7 months ago Reply
You do describe other advantages or rpms, such as versioning and rollback, that my fix does not offer. 7 months ago Reply
The main difference is that we use Maven to build the RPM and then we use Nexus to store the artifacts that Maven creates, both WAR and RPM.
We wrote a Nexus YUM plugin that allows direct access to the RPMs hosted on the Nexus as a YUM repo thereby eliminating additional copying steps in our delivery chain. 7 months ago Reply