kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/www/jakarta-tomcat/Makefile

60 lines
1.7 KiB
Makefile
Raw Normal View History

Add pseudo-category 'java'.
2003-08-23 17:16:36 +02:00
# $NetBSD: Makefile,v 1.40 2003/08/23 15:26:27 jschauma Exp $
Initial import of jakarta-tomcat-3.0, the Apache Project Servlet/Java Server Pages engine. This currently runs as a standalone http server with Servlet/JSP support, and will be usable with Apache Server if/when we have a mod_jserv package. I will look into that next, unless someone is already.
2000-01-12 23:21:34 +01:00
Convert to use buildlink2, bsd.pkg.install.mk, and java-vm.mk.
2002-12-28 22:35:04 +01:00
DISTNAME= jakarta-tomcat-${TOMCAT_VERSION}-src
PKGNAME= ${DISTNAME:S/-src$//}
TOMCAT_VERSION= 3.2.4
Add a 'flush' option to the rc.d script. Bump version to jakarta-tomcat-3.2.4nb1 If you've used tomcat this probably comes under the category of bugfix :)
2002-05-23 17:48:44 +02:00
PKGREVISION= 1
Place WRKSRC where it belongs, to make pkglint happy; ok'ed by wiz.
2003-03-29 13:40:00 +01:00
WRKSRC= ${WRKDIR}/${DISTNAME}
Add pseudo-category 'java'.
2003-08-23 17:16:36 +02:00
CATEGORIES= www java
Convert to use buildlink2, bsd.pkg.install.mk, and java-vm.mk.
2002-12-28 22:35:04 +01:00
MASTER_SITES= http://jakarta.apache.org/builds/jakarta-tomcat/release/v${TOMCAT_VERSION}/src/
Initial import of jakarta-tomcat-3.0, the Apache Project Servlet/Java Server Pages engine. This currently runs as a standalone http server with Servlet/JSP support, and will be usable with Apache Server if/when we have a mod_jserv package. I will look into that next, unless someone is already.
2000-01-12 23:21:34 +01:00
s/netbsd.org/NetBSD.org/
2003-07-18 00:50:55 +02:00
MAINTAINER= jwise@NetBSD.org
Initial import of jakarta-tomcat-3.0, the Apache Project Servlet/Java Server Pages engine. This currently runs as a standalone http server with Servlet/JSP support, and will be usable with Apache Server if/when we have a mod_jserv package. I will look into that next, unless someone is already.
2000-01-12 23:21:34 +01:00
HOMEPAGE= http://jakarta.apache.org/
COMMENT should start with a capital letter.
2003-07-22 06:14:17 +02:00
COMMENT= The Apache Project's Java Servlet 2.2 and JSP 1.1 server
Initial import of jakarta-tomcat-3.0, the Apache Project Servlet/Java Server Pages engine. This currently runs as a standalone http server with Servlet/JSP support, and will be usable with Apache Server if/when we have a mod_jserv package. I will look into that next, unless someone is already.
2000-01-12 23:21:34 +01:00
Mechanical changes to 375 files to change dependency patterns of the form foo-* to foo-[0-9]*. This is to cause the dependencies to match only the packages whose base package name is "foo", and not those named "foo-bar". A concrete example is p5-Net-* matching p5-Net-DNS as well as p5-Net. Also change dependency examples in Packages.txt to reflect this.
2001-09-28 01:17:41 +02:00
DEPENDS+= jakarta-servletapi-[0-9]*:../../www/jakarta-servletapi
Change dependency of jakarta-ant into apache-ant, as it's now known. All build fine with the new version of ant.
2003-06-03 19:02:44 +02:00
DEPENDS+= apache-ant>=1.4.1:../../devel/apache-ant
move line to silence pkglint
2000-09-03 15:38:31 +02:00
Instead of including bsd.pkg.install.mk directly in a package Makefile, have it be automatically included by bsd.pkg.mk if USE_PKGINSTALL is set to "YES". This enforces the requirement that bsd.pkg.install.mk be included at the end of a package Makefile. Idea suggested by Julio M. Merino Vidal <jmmv at menta.net>.
2003-01-28 23:03:00 +01:00
USE_BUILDLINK2= yes
Update jakarta-tomcat to version 3.2.1. Changes in the package since version 3.1.1 (the last pkgsrc version): ===================================================================== * tomcat is now always installed under ${PREFIX}/tomcat. Making ${TOMCAT_HOME} configurable added much complexity for not real gain. It had been my intention to aim for a hier(7) like install for tomcat with this version, but at this point there are way to many hard-coded relative paths (relative to tomcat.home) in tomcat, and in addition, all of the (quite good, really) documentation assumes the standard install paths. Note that the previous default value of ${TOMCAT_HOME} was ${PREFIX}/jakarta/tomcat. * an rc.subr compatible (but not requiring) startup script is now installed as ${PREFIX}/etc/rc.d/tomcat. * if Sun's JSSE (Java Secure Socket Extensions) is in ${CLASSPATH} when the pkg is built, tomcat will be built with support for SSL in the standalone server mode. This soft dependency will be replaced by a hard dependency as soon as I get a chance to import a JSSE package (soon). * likewise, I will import an ap-jk package for the new apache connector (mod_jk) soon. ap-jserv continues to be usable for this purpose. Changes in tomcat itself since version 3.1.1: ============================================= New in tomcat-3.2.1: -------------------- Tomcat 3.2.1 is a maintenance and bug fix release, based on the Tomcat 3.2 (final) code base. The following changes are included: - Disallowed requesting JSP pages under the WEB-INF directory (/WEB-INF/dummy.jsp). Previously, only requests for static files were being disallowed. - The JDBCRealm request interceptor will now log the description of any JDBC exception that occurs, to aid in debugging. SECURITY VULNERABILITIES FIXED IN TOMCAT 3.2.1 (note that these fixes were also made to the tomcat-3.1 branch in tomcat 3.1.1) Protection of Resources in /WEB-INF and /META-INF Directories The servlet specification prohibits servlet containers from serving resources in the /WEB-INF and /META-INF directories of a web application archive directly to clients. In Tomcat 3.2, this means that URLs like: http://localhost:8080/examples/WEB-INF/web.xml will return an error message, rather than the contents of your deployment descriptor. However, there is a vulnerability in Tomcat 3.2 that exposes this information if the client requests a URL like this instead: http://localhost:8080/examples//WEB-INF/web.xml (note the double slash before "WEB-INF"). This vulnerability has been corrected in Tomcat 3.2.1. Show Source Vulnerability The example application delivered with Tomcat 3.2 included a mechanism to display the source code for the JSP page examples. This mechanism could be used to bypass the restrictions on displaying sensitive information in the WEB-INF and META-INF directories. This vulnerability has been removed. New in tomcat-3.2: ------------------ Tomcat 3.2 is mainly a performance tune-up release, although a few new features have been added. - Support for mod_jk, which is a replacement to the elderly mod_jserv, has had several bugs fixed and has received much more testing. It is now recommended that all users use mod_jk instead of mod_jserv. - Support JAXP-based XML parser independence. - New and often requested "how-to" documents covering the following topics: - Configuring workers.properties - IIS and Netscape configuration - Running tomcat inside an IIS or Netscape process - Running Tomcat as a Windows NT service - Configuring a JDBC realm - Configuring mod_jk - First round of policy-based security support intended for running untrusted code inside of Tomcat. Interested users should test this support and post feedback to the Tomcat users mailing list. - SSL support for standalone Tomcat. (Preliminary support first appeared in 3.1, but the support in 3.2 has received more testing and documentation support). - Thread reuse is now enabled by default. The thread pool support code was part of 3.1, but not enabled since it was new. - Support for plug-able session managers. Unfortunately, no how-to documents that support this functionality exist (yet). For the adventurous, be aware that the interface that allows administrators to plug session managers is the normal Interceptor interface. - An almost total rewrite of the HTTP request handling now results in improved performance when running Tomcat stand-alone. - Significantly reduced garbage collection. - The code underwent a refactoring effort resulting in improved readability. - And of course, hundreds of miscellaneous improvements and fixes.
2001-03-28 04:46:07 +02:00
MAKEFILE= build.xml
ALL_TARGET= main
INSTALL_TARGET= dist
Initial import of jakarta-tomcat-3.0, the Apache Project Servlet/Java Server Pages engine. This currently runs as a standalone http server with Servlet/JSP support, and will be usable with Apache Server if/when we have a mod_jserv package. I will look into that next, unless someone is already.
2000-01-12 23:21:34 +01:00
Convert to use buildlink2, bsd.pkg.install.mk, and java-vm.mk.
2002-12-28 22:35:04 +01:00
SAMPLECONFDIR= ${PREFIX}/tomcat/conf
PKG_SYSCONFDIR.jakarta-tomcat= ${SAMPLECONFDIR}
Instead of including bsd.pkg.install.mk directly in a package Makefile, have it be automatically included by bsd.pkg.mk if USE_PKGINSTALL is set to "YES". This enforces the requirement that bsd.pkg.install.mk be included at the end of a package Makefile. Idea suggested by Julio M. Merino Vidal <jmmv at menta.net>.
2003-01-28 23:03:00 +01:00
USE_PKGINSTALL= yes
Convert to use buildlink2, bsd.pkg.install.mk, and java-vm.mk.
2002-12-28 22:35:04 +01:00
OWN_DIRS= ${PREFIX}/tomcat
Use OWN_DIRS instead of MAKE_DIRS, and use the right operator +=. Fixes PR pkg/22039 by Todd Vierling.
2003-07-22 23:35:12 +02:00
OWN_DIRS+= ${PREFIX}/tomcat/conf
OWN_DIRS+= ${PREFIX}/tomcat/logs
OWN_DIRS+= ${PREFIX}/tomcat/webapps
Convert to use buildlink2, bsd.pkg.install.mk, and java-vm.mk.
2002-12-28 22:35:04 +01:00
CFILES= server.xml web.xml tomcat-users.xml jni_server.xml
CFILES+= tomcat.policy workers.properties
CONF_FILES= # empty
.for FILE in ${CFILES}
CONF_FILES+= ${SAMPLECONFDIR}/${FILE}.default ${PKG_SYSCONFDIR}/${FILE}
.endfor
RCD_SCRIPTS= tomcat
Initial import of jakarta-tomcat-3.0, the Apache Project Servlet/Java Server Pages engine. This currently runs as a standalone http server with Servlet/JSP support, and will be usable with Apache Server if/when we have a mod_jserv package. I will look into that next, unless someone is already.
2000-01-12 23:21:34 +01:00
Use the JAVA_HOME of the JDK upon which the jakarta-tomcat package depends as the default JAVA_HOME. It can still be overridden by an environment variable.
2002-12-28 23:34:13 +01:00
FILES_SUBST+= JAVA_HOME=${PKG_JAVA_HOME}
Ease out-of-the-box integration with mod_jk (pkgsrc/www/ap-jk): * include a workers.properties which works out of the box -- this file may be better off as part of the ap-jk package, even though it is somewhat tomcat-specific. I'll give this possibility more thought. * modify the apache config file fragment generator which runs on tomcat startup to generate an Include-able apache config file fragment which works out of the box to laod mod_jk.
2001-03-30 01:26:24 +02:00
post-patch:
Convert to use buildlink2, bsd.pkg.install.mk, and java-vm.mk.
2002-12-28 22:35:04 +01:00
${FIND} ${WRKSRC} -name "*.orig" -print | ${XARGS} ${RM} -f
for file in ${WRKSRC}/src/etc/workers.properties; do \
${SED} -e "s|@PREFIX@|${PREFIX}|g" \
-e "s|@JAVA_HOME@|${PKG_JAVA_HOME}|g" \
$$file > $$file.tmp; \
${MV} -f $$file.tmp $$file; \
done
Initial import of jakarta-tomcat-3.0, the Apache Project Servlet/Java Server Pages engine. This currently runs as a standalone http server with Servlet/JSP support, and will be usable with Apache Server if/when we have a mod_jserv package. I will look into that next, unless someone is already.
2000-01-12 23:21:34 +01:00
Update jakarta-tomcat to version 3.2.1. Changes in the package since version 3.1.1 (the last pkgsrc version): ===================================================================== * tomcat is now always installed under ${PREFIX}/tomcat. Making ${TOMCAT_HOME} configurable added much complexity for not real gain. It had been my intention to aim for a hier(7) like install for tomcat with this version, but at this point there are way to many hard-coded relative paths (relative to tomcat.home) in tomcat, and in addition, all of the (quite good, really) documentation assumes the standard install paths. Note that the previous default value of ${TOMCAT_HOME} was ${PREFIX}/jakarta/tomcat. * an rc.subr compatible (but not requiring) startup script is now installed as ${PREFIX}/etc/rc.d/tomcat. * if Sun's JSSE (Java Secure Socket Extensions) is in ${CLASSPATH} when the pkg is built, tomcat will be built with support for SSL in the standalone server mode. This soft dependency will be replaced by a hard dependency as soon as I get a chance to import a JSSE package (soon). * likewise, I will import an ap-jk package for the new apache connector (mod_jk) soon. ap-jserv continues to be usable for this purpose. Changes in tomcat itself since version 3.1.1: ============================================= New in tomcat-3.2.1: -------------------- Tomcat 3.2.1 is a maintenance and bug fix release, based on the Tomcat 3.2 (final) code base. The following changes are included: - Disallowed requesting JSP pages under the WEB-INF directory (/WEB-INF/dummy.jsp). Previously, only requests for static files were being disallowed. - The JDBCRealm request interceptor will now log the description of any JDBC exception that occurs, to aid in debugging. SECURITY VULNERABILITIES FIXED IN TOMCAT 3.2.1 (note that these fixes were also made to the tomcat-3.1 branch in tomcat 3.1.1) Protection of Resources in /WEB-INF and /META-INF Directories The servlet specification prohibits servlet containers from serving resources in the /WEB-INF and /META-INF directories of a web application archive directly to clients. In Tomcat 3.2, this means that URLs like: http://localhost:8080/examples/WEB-INF/web.xml will return an error message, rather than the contents of your deployment descriptor. However, there is a vulnerability in Tomcat 3.2 that exposes this information if the client requests a URL like this instead: http://localhost:8080/examples//WEB-INF/web.xml (note the double slash before "WEB-INF"). This vulnerability has been corrected in Tomcat 3.2.1. Show Source Vulnerability The example application delivered with Tomcat 3.2 included a mechanism to display the source code for the JSP page examples. This mechanism could be used to bypass the restrictions on displaying sensitive information in the WEB-INF and META-INF directories. This vulnerability has been removed. New in tomcat-3.2: ------------------ Tomcat 3.2 is mainly a performance tune-up release, although a few new features have been added. - Support for mod_jk, which is a replacement to the elderly mod_jserv, has had several bugs fixed and has received much more testing. It is now recommended that all users use mod_jk instead of mod_jserv. - Support JAXP-based XML parser independence. - New and often requested "how-to" documents covering the following topics: - Configuring workers.properties - IIS and Netscape configuration - Running tomcat inside an IIS or Netscape process - Running Tomcat as a Windows NT service - Configuring a JDBC realm - Configuring mod_jk - First round of policy-based security support intended for running untrusted code inside of Tomcat. Interested users should test this support and post feedback to the Tomcat users mailing list. - SSL support for standalone Tomcat. (Preliminary support first appeared in 3.1, but the support in 3.2 has received more testing and documentation support). - Thread reuse is now enabled by default. The thread pool support code was part of 3.1, but not enabled since it was new. - Support for plug-able session managers. Unfortunately, no how-to documents that support this functionality exist (yet). For the adventurous, be aware that the interface that allows administrators to plug session managers is the normal Interceptor interface. - An almost total rewrite of the HTTP request handling now results in improved performance when running Tomcat stand-alone. - Significantly reduced garbage collection. - The code underwent a refactoring effort resulting in improved readability. - And of course, hundreds of miscellaneous improvements and fixes.
2001-03-28 04:46:07 +02:00
post-install:
Quick fix for apache.org security advisory -- example webapps as present have a cross-site scripting vulnerability. For now, we remove them, but we will update to a newer version when one is available.
2002-04-09 20:24:51 +02:00
${RM} ${PREFIX}/tomcat/webapps/examples.war
Initial import of jakarta-tomcat-3.0, the Apache Project Servlet/Java Server Pages engine. This currently runs as a standalone http server with Servlet/JSP support, and will be usable with Apache Server if/when we have a mod_jserv package. I will look into that next, unless someone is already.
2000-01-12 23:21:34 +01:00
Convert to use buildlink2, bsd.pkg.install.mk, and java-vm.mk.
2002-12-28 22:35:04 +01:00
.include "../../mk/java-vm.mk"
Initial import of jakarta-tomcat-3.0, the Apache Project Servlet/Java Server Pages engine. This currently runs as a standalone http server with Servlet/JSP support, and will be usable with Apache Server if/when we have a mod_jserv package. I will look into that next, unless someone is already.
2000-01-12 23:21:34 +01:00
.include "../../mk/bsd.pkg.mk"
Convert to use buildlink2, bsd.pkg.install.mk, and java-vm.mk.
2002-12-28 22:35:04 +01:00
Update jakarta-tomcat to version 3.2.1. Changes in the package since version 3.1.1 (the last pkgsrc version): ===================================================================== * tomcat is now always installed under ${PREFIX}/tomcat. Making ${TOMCAT_HOME} configurable added much complexity for not real gain. It had been my intention to aim for a hier(7) like install for tomcat with this version, but at this point there are way to many hard-coded relative paths (relative to tomcat.home) in tomcat, and in addition, all of the (quite good, really) documentation assumes the standard install paths. Note that the previous default value of ${TOMCAT_HOME} was ${PREFIX}/jakarta/tomcat. * an rc.subr compatible (but not requiring) startup script is now installed as ${PREFIX}/etc/rc.d/tomcat. * if Sun's JSSE (Java Secure Socket Extensions) is in ${CLASSPATH} when the pkg is built, tomcat will be built with support for SSL in the standalone server mode. This soft dependency will be replaced by a hard dependency as soon as I get a chance to import a JSSE package (soon). * likewise, I will import an ap-jk package for the new apache connector (mod_jk) soon. ap-jserv continues to be usable for this purpose. Changes in tomcat itself since version 3.1.1: ============================================= New in tomcat-3.2.1: -------------------- Tomcat 3.2.1 is a maintenance and bug fix release, based on the Tomcat 3.2 (final) code base. The following changes are included: - Disallowed requesting JSP pages under the WEB-INF directory (/WEB-INF/dummy.jsp). Previously, only requests for static files were being disallowed. - The JDBCRealm request interceptor will now log the description of any JDBC exception that occurs, to aid in debugging. SECURITY VULNERABILITIES FIXED IN TOMCAT 3.2.1 (note that these fixes were also made to the tomcat-3.1 branch in tomcat 3.1.1) Protection of Resources in /WEB-INF and /META-INF Directories The servlet specification prohibits servlet containers from serving resources in the /WEB-INF and /META-INF directories of a web application archive directly to clients. In Tomcat 3.2, this means that URLs like: http://localhost:8080/examples/WEB-INF/web.xml will return an error message, rather than the contents of your deployment descriptor. However, there is a vulnerability in Tomcat 3.2 that exposes this information if the client requests a URL like this instead: http://localhost:8080/examples//WEB-INF/web.xml (note the double slash before "WEB-INF"). This vulnerability has been corrected in Tomcat 3.2.1. Show Source Vulnerability The example application delivered with Tomcat 3.2 included a mechanism to display the source code for the JSP page examples. This mechanism could be used to bypass the restrictions on displaying sensitive information in the WEB-INF and META-INF directories. This vulnerability has been removed. New in tomcat-3.2: ------------------ Tomcat 3.2 is mainly a performance tune-up release, although a few new features have been added. - Support for mod_jk, which is a replacement to the elderly mod_jserv, has had several bugs fixed and has received much more testing. It is now recommended that all users use mod_jk instead of mod_jserv. - Support JAXP-based XML parser independence. - New and often requested "how-to" documents covering the following topics: - Configuring workers.properties - IIS and Netscape configuration - Running tomcat inside an IIS or Netscape process - Running Tomcat as a Windows NT service - Configuring a JDBC realm - Configuring mod_jk - First round of policy-based security support intended for running untrusted code inside of Tomcat. Interested users should test this support and post feedback to the Tomcat users mailing list. - SSL support for standalone Tomcat. (Preliminary support first appeared in 3.1, but the support in 3.2 has received more testing and documentation support). - Thread reuse is now enabled by default. The thread pool support code was part of 3.1, but not enabled since it was new. - Support for plug-able session managers. Unfortunately, no how-to documents that support this functionality exist (yet). For the adventurous, be aware that the interface that allows administrators to plug session managers is the normal Interceptor interface. - An almost total rewrite of the HTTP request handling now results in improved performance when running Tomcat stand-alone. - Significantly reduced garbage collection. - The code underwent a refactoring effort resulting in improved readability. - And of course, hundreds of miscellaneous improvements and fixes.
2001-03-28 04:46:07 +02:00
MAKE_PROGRAM= ${LOCALBASE}/bin/ant
Move MAKE_FLAGS= to after .include "../../mk/bsd.pkg.mk" to ensure it overrides any external settings
2002-03-26 17:37:26 +01:00
MAKE_FLAGS= -Dpkgsrc.prefix=${PREFIX}
Convert to use buildlink2, bsd.pkg.install.mk, and java-vm.mk.
2002-12-28 22:35:04 +01:00
CLASSPATH:= ${LOCALBASE}/lib/java/servlet.jar:${LOCALBASE}/lib/jaxp.jar:${LOCALBASE}/lib/parser.jar:${CLASSPATH}
Reference in a new issue Copy permalink