Rainer Jung wrote:
If you put the jk modules into your apache rpm, you couple the
lifecycle of those two together. So you need to build and deliver a
new rpm whenever at least one of apache httpd and of jk have a new
version, you want to deploy.
The release cycles of httpd and jk are very dif
Dan Ciarniello wrote:
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan,
Dan Ciarniello wrote:
I am putting together RPMs for apache and tomcat and I want to
include the mod_jk connector with the apache RPM
:(
Don't do that; instead, have a separate RPM th
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan,
Dan Ciarniello wrote:
I am putting together RPMs for apache and tomcat and I want to
include the mod_jk connector with the apache RPM
:(
Don't do that; instead, have a separate RPM that just contains mod_j
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan,
Dan Ciarniello wrote:
> I am putting together RPMs for apache and tomcat and I want to
> include the mod_jk connector with the apache RPM
:(
Don't do that; instead, have a separate RPM that just contains mod_jk
and maybe a script to install it
I am putting together RPMs for apache and tomcat and I want to include
the mod_jk connector with the apache RPM but I get an error that apxs
cannot be found even though I give the full path to apxs.
The commands that I do are
(in apache)
./configure --enable-ssl=shared --enable-so --with-ldap
