You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Jan Harmsen <ja...@softwareag.com> on 2003/08/12 09:27:23 UTC

Tomcat-5.0.7 build fails behind firewall due to missing commons-daemon

Hi,

when trying to build Tomcat-5.0.7 from scratch behind a firewall (using
http proxy) build fails due to missing commons-daemon:

Environment: Linux (SuSE 8.2)


     [echo] ========== Building: commons-daemon 

BUILD FAILED
/home/jan/jakarta-tomcat-5.0.7-src/src/jakarta-tomcat-5/build.xml:485:
Basedir
/home/jan/jakarta-tomcat-5.0.7-src/src/jakarta-commons-sandbox/daemon
does not exist


The problem is that commons-daemon is neither part of the
Tomcat-5.0.7-src nor is it available as a release from
http://www.apache.org/dist/jakarta/commons/ but has to be downloaded
as a nightly build from
http://cvs.apache.org/builds/jakarta-commons/nightly/commons-daemon/
which means the filename changes and has to be built dynamically within
build.xml

To make Tomcat-5.0.7 build.xml work when proxy.use=on either build.xml
has to be modified to download commons-daemon and unzip it into the
Tomcat-source-dir or commons-daemon has to be included into the
Tomcat-5.0.7-src.

Making commons-daemon available as a release at
http://www.apache.org/dist/jakarta/commons/ or setting a symbolic link
like commons-daemon-current.tar.gz would of course reduce the effort
because the filename wouldn't have to be build dynamically.

Which solution is suggested ?

Best regards,

Jan

Re: Tomcat-5.0.7 build fails behind firewall due to missing commons-daemon

Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
Jan Harmsen wrote:
> Hi,
> 
> when trying to build Tomcat-5.0.7 from scratch behind a firewall (using
> http proxy) build fails due to missing commons-daemon:
> 
> Environment: Linux (SuSE 8.2)
> 
> 
>      [echo] ========== Building: commons-daemon 
> 
> BUILD FAILED
> /home/jan/jakarta-tomcat-5.0.7-src/src/jakarta-tomcat-5/build.xml:485:
> Basedir
> /home/jan/jakarta-tomcat-5.0.7-src/src/jakarta-commons-sandbox/daemon
> does not exist
> 
> 
> The problem is that commons-daemon is neither part of the
> Tomcat-5.0.7-src nor is it available as a release from
> http://www.apache.org/dist/jakarta/commons/ but has to be downloaded
> as a nightly build from
> http://cvs.apache.org/builds/jakarta-commons/nightly/commons-daemon/
> which means the filename changes and has to be built dynamically within
> build.xml
> 
> To make Tomcat-5.0.7 build.xml work when proxy.use=on either build.xml
> has to be modified to download commons-daemon and unzip it into the
> Tomcat-source-dir or commons-daemon has to be included into the
> Tomcat-5.0.7-src.
> 
> Making commons-daemon available as a release at
> http://www.apache.org/dist/jakarta/commons/ or setting a symbolic link
> like commons-daemon-current.tar.gz would of course reduce the effort
> because the filename wouldn't have to be build dynamically.
> 
> Which solution is suggested ?

Making a release of commons-daemon would be the best.
I am working on it... But very slowly :-(

> 
> Best regards,
> 
> Jan
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> 
>

Re: Tomcat-5.0.7 build fails behind firewall due to missing commons-daemon

Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
Jan Harmsen wrote:
> Hi,
> 
> when trying to build Tomcat-5.0.7 from scratch behind a firewall (using
> http proxy) build fails due to missing commons-daemon:
> 
> Environment: Linux (SuSE 8.2)
> 
> 
>      [echo] ========== Building: commons-daemon 
> 
> BUILD FAILED
> /home/jan/jakarta-tomcat-5.0.7-src/src/jakarta-tomcat-5/build.xml:485:
> Basedir
> /home/jan/jakarta-tomcat-5.0.7-src/src/jakarta-commons-sandbox/daemon
> does not exist
> 
> 
> The problem is that commons-daemon is neither part of the
> Tomcat-5.0.7-src nor is it available as a release from
> http://www.apache.org/dist/jakarta/commons/ but has to be downloaded
> as a nightly build from
> http://cvs.apache.org/builds/jakarta-commons/nightly/commons-daemon/
> which means the filename changes and has to be built dynamically within
> build.xml
> 
> To make Tomcat-5.0.7 build.xml work when proxy.use=on either build.xml
> has to be modified to download commons-daemon and unzip it into the
> Tomcat-source-dir or commons-daemon has to be included into the
> Tomcat-5.0.7-src.
> 
> Making commons-daemon available as a release at
> http://www.apache.org/dist/jakarta/commons/ or setting a symbolic link
> like commons-daemon-current.tar.gz would of course reduce the effort
> because the filename wouldn't have to be build dynamically.
> 
> Which solution is suggested ?

Making a release of commons-daemon would be the best.
I am working on it... But very slowly :-(

> 
> Best regards,
> 
> Jan
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> 
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org