View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20041105223732

BUILD FAILED
Ant Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:59: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:34: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/
Date of build: 11/05/2004 22:37:32
Time to build: 12 minutes 50 seconds
Last changed: 11/05/2004 21:58:33
Last log entry: Add a test of accessing a secured servlet under a web-resource-collection constraint that does not specify any http-methods

 Unit Tests: (0)  Total Errors and Failures: (0)
 

 Modifications since last build:  (49)
1.25modifiedstarksmtestsuite/src/main/org/jboss/test/web/test/WebIntegrationUnitTestCase.javaAdd a test of accessing a secured servlet under a web-resource-collection constraint that does not specify any http-methods
1.19modifiedstarksmtestsuite/src/resources/web/WEB-INF/jbosstest-web.xmlAdd a web-resource-collection that does not specify any http-methods and add a second mapping of the SecureServlet under this url-pattern.
1.3modifiedstarksmtestsuite/src/main/org/jboss/test/security/test/WebResourcePermissionUnitTestCase.javaAdd a test of an empty http methods String[] equating to an empty or null http methods string.
1.6modifiedstarksmj2ee/src/main/javax/security/jacc/WebUserDataPermission.javaAdd the missing serialVersionUID
1.6modifiedstarksmj2ee/src/main/javax/security/jacc/WebResourcePermission.javaThe handling of an empty http methods String[] should have been producing a null httpMethods set to indicate all methods were allowed. Instead it was producing an empty httpMethods set which disallowed all access. Fixes [ 1054897 ] JACC incorrect when checking auth for WebResourcePermission.
1.5modifiedstarksmtestsuite/src/main/org/jboss/test/web/test/FormAuthUnitTestCase.javaAdd a testFlushOnSessionInvalidation that validates that a war which uses <security-domain flushOnSessionInvalidation="true"> in the jboss-web.xml does not have any jaas security domain cache entries after the web session has been invalidated.
1.1addedrecampbelltools/etc/cruisecontrol/scripts/cc-config-3.2-jdk-matrix.xmlextracted matrix & testsuite to seperate proejcts for each branch
1.1addedrecampbelltools/etc/cruisecontrol/scripts/cc-config-3.2-testsuite.xmlextracted matrix & testsuite to seperate proejcts for each branch
1.3modifiedrecampbelltools/etc/cruisecontrol/scripts/cc-config-3.2.xmlextracted matrix & testsuite to seperate proejcts for each branch
1.1addedrecampbelltools/etc/cruisecontrol/scripts/cc-config-4.0-jdk-matrix.xmlextracted matrix & testsuite to seperate proejcts for each branch
1.1addedrecampbelltools/etc/cruisecontrol/scripts/cc-config-4.0-testsuite.xmlextracted matrix & testsuite to seperate proejcts for each branch
1.3modifiedrecampbelltools/etc/cruisecontrol/scripts/cc-config-4.0.xmlextracted matrix & testsuite to seperate proejcts for each branch
1.1addedrecampbelltools/etc/cruisecontrol/scripts/cc-config-head-jdk-matrix.xmlextracted matrix & testsuite to seperate proejcts for each branch
1.5modifiedrecampbelltools/etc/cruisecontrol/scripts/cc-config.xmlextracted matrix & testsuite to seperate proejcts for each branch
1.2deletedrecampbelltools/etc/cruisecontrol/scripts/cc-config-head-jdks.xmlrenamed to -jdk-matrix
1.3modifiedrecampbelltools/etc/cruisecontrol/scripts/do_test.shuse env props instead of property file for node defs
1.25modifiedbwang00cache/docs/Changelog.txtUpdated
1.1addedpatriot1burkeaspects/build-test.xmlrefactored asynchronous again so that it works under JDK 1.4
1.2modifiedpatriot1burkeaspects/build-test50.xmlrefactored asynchronous again so that it works under JDK 1.4
1.21modifiedpatriot1burkeaspects/build.xmlrefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/test/org/jboss/test/asynch/POJO.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/test/org/jboss/test/asynch/Service.javarefactored asynchronous again so that it works under JDK 1.4
1.2modifiedpatriot1burkeaspects/src/test50/org/jboss/test/asynch/AsynchTestCase.javarefactored asynchronous again so that it works under JDK 1.4
1.2modifiedpatriot1burkeaspects/src/test50/org/jboss/test/asynch/POJO.javarefactored asynchronous again so that it works under JDK 1.4
1.2modifiedpatriot1burkeaspects/src/test50/org/jboss/test/asynch/Service.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/test/org/jboss/test/asynch/AsynchTestCase.javarefactored asynchronous again so that it works under JDK 1.4
1.2deletedpatriot1burkeaspects/src/jdk15/org/jboss/aspects/asynchronous/AsynchAspect.javarefactored asynchronous again so that it works under JDK 1.4
1.2deletedpatriot1burkeaspects/src/jdk15/org/jboss/aspects/asynchronous/AsynchMixin.javarefactored asynchronous again so that it works under JDK 1.4
1.2deletedpatriot1burkeaspects/src/jdk15/org/jboss/aspects/asynchronous/AsynchProvider.javarefactored asynchronous again so that it works under JDK 1.4
1.2deletedpatriot1burkeaspects/src/jdk15/org/jboss/aspects/asynchronous/AsynchProxyInterceptor.javarefactored asynchronous again so that it works under JDK 1.4
1.2deletedpatriot1burkeaspects/src/jdk15/org/jboss/aspects/asynchronous/AsynchProxyMixin.javarefactored asynchronous again so that it works under JDK 1.4
1.2deletedpatriot1burkeaspects/src/jdk15/org/jboss/aspects/asynchronous/AsynchRemoting.javarefactored asynchronous again so that it works under JDK 1.4
1.2deletedpatriot1burkeaspects/src/jdk15/org/jboss/aspects/asynchronous/Asynchronous.javarefactored asynchronous again so that it works under JDK 1.4
1.2deletedpatriot1burkeaspects/src/jdk15/org/jboss/aspects/asynchronous/FutureHolder.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/main/org/jboss/aspects/asynch/AsynchAspect.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/main/org/jboss/aspects/asynch/AsynchMixin.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/main/org/jboss/aspects/asynch/AsynchProvider.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/main/org/jboss/aspects/asynch/AsynchProxyInterceptor.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/main/org/jboss/aspects/asynch/AsynchProxyMixin.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/main/org/jboss/aspects/asynch/AsynchRemoting.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/main/org/jboss/aspects/asynch/Asynchronous.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/main/org/jboss/aspects/asynch/ExecutorAbstraction.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/main/org/jboss/aspects/asynch/Future.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/main/org/jboss/aspects/asynch/FutureHolder.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/main/org/jboss/aspects/asynch/FutureImpl.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/main/org/jboss/aspects/asynch/TimeoutException.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/jdk15/org/jboss/aspects/asynch/Asynchronous.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/jdk15/org/jboss/aspects/asynch/ExecutorAbstraction.javarefactored asynchronous again so that it works under JDK 1.4
1.1addedpatriot1burkeaspects/src/jdk15/org/jboss/aspects/asynch/FutureImpl.javarefactored asynchronous again so that it works under JDK 1.4

Reply via email to