[OWASP-ESAPI] All WAF tests pass

[Ed Schaller]

> The build/test standard is Java 5 right now. I say, if the tests
> pass in Java 5 release 22 (the •final• Java 5 public release) in
> Linux+Windows, then we are good to go.
> 
> I do not recommend doing any ESAPI core development w/ Java 6.

I've been meaning to verify in 1.5...

java version "1.5.0_20"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_20-b02)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_20-b02, mixed mode)

Debian Sid:

Results :

Tests run: 427, Failures: 0, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------

Once I figure out how to point mvn at a different JDK install (or why
update-java-alternatives isn't working for make-jpkg jdk installs)
I'll test with IBM's jdk.

Just because I have them installed and update-java-alternatives is
working for them:

java version "1.6.0_0"
OpenJDK Runtime Environment (IcedTea6 1.6.1) (6b16-1.6.1-2)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)

Tests in error: 
  testSetExpirationTime(org.owasp.esapi.reference.UserTest)

Tests run: 427, Failures: 0, Errors: 1, Skipped: 0


java version "1.5.0"
gij (GNU libgcj) version 4.3.4

Compiles but surefire itself is failing to run the tests in the first
place.

>>>------>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
Url : https://lists.owasp.org/pipermail/owasp-esapi/attachments/20091120/f8793968/attachment.bin