Several people pointed out that mandatory testing in Maven can be weakened by setting the maven.test.failure.ignore or maven.test.skip system properties. Thanks! That is helpful. However, I still think the default behavior is too draconian. It leads to people turning off breaking tests and forgetting about them rather than fixing them. Just this morning I found an example of that in Jaxen, where the test that should have caught a regression had been turned off some months ago to enable the build. Nobody remembered to turn it back on when we "fixed" the problem. Thus nobody noticed the problem still existed.
The Jakarta Apache Project has released version 5.5.9 of the Tomcat open source servlet container and official reference implementation of the Java Servlet API 2.4 and Java Server Pages (JSP) 2.0. This release is considere to be production worthy, and all 5.5.x users are encouraged to upgrade. "Tomcat 5.5 is designed to run on J2SE 5.0 and later, and requires configuration to run on J2SE 1.4....In addition, Tomcat 5.5 uses the Eclipse JDT Java compiler for compiling JSP pages. This means you no longer need to have the complete Java Development Kit (JDK) to run Tomcat, but a Java Runtime Environment (JRE) is sufficient. The Eclipse JDT Java compiler is bundled with the binary Tomcat distributions. Tomcat can also be configured to use the compiler from the JDK to compile JSPs, or any other Java compiler supported by Apache Ant."
The Jakarta Apache Project has posted the second release candidate of HTTPClient 3.0. New features in 3.0 include:
According to the announcement, "Several minor issues have been fixed since RC1 and HttpClient 3.0 has made significant progess towards the final release. We are confident HttpClient 3.0 is ready to replace HttpClient 2.0 as a production quality release. We strongly recommend upgrading to HttpClient 3.0. Please download and enjoy."