Rudder

Currently our packages provide rudder-webapp and rudder-inventory-endpoint in independant packages, but they depend on rudder-jetty (our re-packaged version of jetty, which is basically the same as upstream). This imposes a strong constraint on the version of jetty to use, and some users would like to use their own version of jetty, or the one provided by their OS.

We should rework the packaging to:

1. On Debian systems, rudder-webapp and rudder-inventory-endpoint should depend on "rudder-jetty | jetty | jetty8" (see https://packages.debian.org/search?keywords=jetty)
2. On RPM systems, use virtual package names (via the "Provides" feature), by adapting the rudder-jetty package to provide the virtual package name and adapting rudder-webapp and rudder-inventory-endpoint to depend on the virtual package name. This is made slightly trickier by the fact that different distributions provide different virtual names for jetty (see table below), but this can easily be managed using RPM spec's 'if %{x}' macros
3. Adapt both packages to install the webapps under /opt/rudder/share/webapps (instead of /opt/rudder/jetty7/webapps)
4. Adapt the context file (rudder.xml) to use a the new path to the WAR

• RHEL 6 : jetty-eclipse
• Fedora : jetty-server
• SLES 11 : SLES does not package jetty. Seriously. Just depend on rudder-jetty.