tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lar...@apache.org
Subject cvs commit: jakarta-tomcat README
Date Tue, 13 Feb 2001 04:37:27 GMT
larryi      01/02/12 20:37:27

  Modified:    .        README
  Log:
  Update section on testing, since the sanity-test is no longer build by
  default.
  
  Revision  Changes    Path
  1.13      +18 -12    jakarta-tomcat/README
  
  Index: README
  ===================================================================
  RCS file: /home/cvs/jakarta-tomcat/README,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- README	2001/02/12 15:06:13	1.12
  +++ README	2001/02/13 04:37:26	1.13
  @@ -177,19 +177,25 @@
   Testing the Build
   =================
   
  -Tomcat includes a small web application with some quick tests to exercize
  -the various parts of the server.  It is built automatically, along with the
  -rest of Tomcat, by the steps described above.  To run the tests against the
  -"unpacked" build, for example, you first need to set the Admin application
  -to "trusted".  This can be accomplished by executing the following:
  +Tomcat includes a "test" web application with some quick tests to exercise
  +the various parts of the Tomcat container.  This test is not built by
  +default.  To add the "test" web application to your "unpackaged" build,
  +execute:
  +
  +	cd $JAKARTA_HOME/jakarta-tomcat
  +	./build.sh sanity-test  <-- Unix
  +	build sanity-test       <-- Windows
   
  +Before you can run the test, you must set the Admin web application to
  +"trusted". This can be accomplished by executing the following:
  +
   	cd $JAKARTA_HOME/build/tomcat	<-- Unix
   	./bin/tomcat.sh run -enableAdmin
   
   	cd %JAKARTA_HOME%\build\tomcat	<-- Windows
   	bin\tomcat run -enableAdmin
   
  -After this, start tomcat with: 
  +Next, start Tomcat with: 
   
   	./bin/startup.sh	<-- Unix
   	bin\startup		<-- Windows
  @@ -205,12 +211,12 @@
   binary distribution which is created in "$JAKARTA_HOME/dist/tomcat".
   
   For security reasons, after you are done with the test, you should either
  -restore the Admin application to the default "untrusted" state, or change
  -the password for the "admin" user. To restore the Admin application to the
  -default "untrusted" state, change trusted="true" to trusted="false" in the
  -"apps-admin.xml" file found in Tomcat's "conf" directory. If you want to
  -leave the Admin application as "trusted, you should change the password for
  -the "admin" user in the "admin-users.xml" file located in Tomcat's
  +restore the Admin web application to the default "untrusted" state, or change
  +the password for the "admin" user. To restore the Admin web application to
  +the default "untrusted" state, change trusted="true" to trusted="false" in
  +the "apps-admin.xml" file found in Tomcat's "conf" directory. If you want to
  +leave the Admin web application as "trusted, you should change the password
  +for the "admin" user in the "admin-users.xml" file located in Tomcat's
   "conf/users" directory.
   
   You can also use the Watchdog compatibility test suite, also available at
  
  
  

Mime
View raw message