GitHub-Spring
/
spring-security
mirror of https://github.com/spring-projects/spring-security.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Spring Security
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
116 Commits
49 Branches
370 Tags
129 MiB
 
 
 
 
Tree: fb753bde38
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'fb753bde38'
${ noResults }
spring-security/integration-test
Ben Alex 862f45e02f
Initial commit. 		22 years ago
..
container-configs Removed leading slash, for compatibility with file existence checking at container adapter startup. 22 years ago
lib Initial commit. 22 years ago
src/net/sf/acegisecurity/integrationtests/web Initial commit. 22 years ago
.cvsignore Initial commit. 22 years ago
build.xml Correct report summarisation, and add support for testing both WAR versions of Contact sample application. 22 years ago
project.properties Modifications to support changes to build.xml. 22 years ago
readme.txt Correct usage instructions. 22 years ago

readme.txt 

===============================================================================
               ACEGI SECURITY SYSTEM FOR SPRING - INTEGRATION TESTS
===============================================================================

This directory allows execution of "in container" integration tests. To run
the tests, the original distribution files for various containers are required
to be placed into the containers directory. These are not included in CVS or 
ZIP releases due to their large size.

To execute these tests:

1. The following files should be placed into the containers directory:

   Jetty-4.2.18-all.zip         (see http://mortbay.jetty.org)
   jakarta-tomcat-5-0.19.zip    (see http://jakarta.apache.org/tomcat)
   jakarta-tomcat-4-1.30.zip    (see http://jakarta.apache.org/tomcat)
   jboss-3.2.3.zip              (see http://www.jboss.org)

2. Shutdown any container or service bound to port 8080.

3. Run "ant tests" (you can safely ignore the console output).

4. At the completion of execution, a summary report will be displayed on the
   console.

$Id$