>Number: 3404 >Category: mod_jserv >Synopsis: JServe ./configure destroys Apache configuration >Confidential: no >Severity: non-critical >Priority: medium >Responsible: jserv >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Sun Nov 15 21:50:01 PST 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.3 >Environment: FreeBSD ns.digidemic.com 2.2.6-RELEASE FreeBSD 2.2.6-RELEASE #0: >Description: In configuring JServ using "./configure --with-apache-dir=... --enable-apache-conf --prefix=... --with-jdk-home=...", my Apache server configuration got blown away. The correct way for JServ to configure the server would have been to have it fork config.status with additional arguments, not configure, and other arguments would have been maintained. >How-To-Repeat: Install Apache with arguments to configure, then configure JServ with --enable-apache-conf. >Fix: have JServ config fork config.status with additional arguments, not configure >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
