From: markt
-Use File->New Project to create a new Java project -for each of the binaries repository (e.g., /usr/share/java), -container, connectors, jasper, servletapi. -Unless you thought ahead to make the ${tomcat.source} directory be under -your Workspace folder, tell Eclipse the external location using "Import/Export...", -General->Existing Project into Workspace. +Use File->Import and chose "Existing Projects into Workspace". +From there import the root directory where you have checked out tomcat.
-Eclipse .project and .classpath files are provided in each of these
-directories so Eclipse should find all source trees and jars, and
+Eclipse .project and .classpath files are provided in to root directory of tomcat repository
+should allow Eclipse to find all source trees and jars, and
hopefully compile without problems. Note that these
files assume you are using Eclipse with a 5.0 or later JDK; also, the
connectors module must be built with a compiler compliance level of 5.0.
diff --git a/webapps/docs/cgi-howto.xml b/webapps/docs/cgi-howto.xml
index d2a682d7a..057b6317c 100644
--- a/webapps/docs/cgi-howto.xml
+++ b/webapps/docs/cgi-howto.xml
@@ -59,11 +59,12 @@ will bypass your security policy configuration in catalina.policy.<
Remove the XML comments from around the CGI servlet and servlet-mapping
configuration in $CATALINA_BASE/conf/web.xml.
Only Contexts which are marked as privileged may use the CGI servlet (see the privileged property of the Context element).
+ +There are several servlet init parameters which can be used to diff --git a/webapps/docs/security-manager-howto.xml b/webapps/docs/security-manager-howto.xml index 5ae498040..0701f6b18 100644 --- a/webapps/docs/security-manager-howto.xml +++ b/webapps/docs/security-manager-howto.xml @@ -180,7 +180,6 @@ grant [signedBy <signer>,] [codeBase <code source>] { // // * Read access to the document root directory // -// $Id$ // ============================================================================