February 2009

Categories

• About Us
• Agitation
• Continuous Integration
• DT Economics
• Developer Testing
• General
• Individual Weblogs
  • Alberto Savoia
  • Ashish Kumar
  • Bob Evans
  • Jeffrey Fredrick
  • Karl Pauls
  • Ken Koster
  • Kent Mitchell
  • Kevin Lawrence
  • Patrick Smith
  • Rob Heiser
  • Vandana Shah
• Managed Developer Testing
• Research in Testing
• Test Driven Development
• The XPeriment

Monthly Archives

• February 2009
• November 2008
• September 2008
• July 2008
• April 2008
• March 2008
• January 2008
• December 2007
• November 2007
• October 2007
• September 2007
• August 2007
• July 2007
• June 2007
• May 2007
• April 2007
• March 2007
• February 2007
• January 2007
• December 2006
• November 2006
• September 2006
• August 2006
• July 2006
• June 2006
• May 2006
• April 2006
• March 2006
• February 2006
• January 2006
• December 2005
• November 2005
• October 2005
• September 2005
• August 2005
• July 2005
• June 2005
• May 2005
• April 2005
• March 2005
• February 2005
• January 2005
• December 2004
• November 2004
• October 2004
• September 2004
• July 2004
• May 2004
• April 2004
• March 2004
• February 2004
• January 2004
• December 2003

Recent Entries

• CruiseControl 2.8 Released

« September 2008 | Homepage | February 2009 »

November 2008 Archives

Nov 21, 2008

–

CruiseControl 2.8 Released 2.8 is now available for download. Along with a number of bug fixes and enhancements (release notes) there have been a number of significant below the surface changes that should be invisible out of the box but will be a GoodThing: Java 5 required to run: this allows us to update the code to more modern Java and to take advantage of the libraries that are part of Java 5 but not Java 1.5. (Of course you can still compile your projects with JDK 1.4.) Upgraded Jetty: along with the upgrade we are also exposing the Jetty configuration files to allow more extensions to the default behavior. Updated to Servlet API 2.5 and JSP API 2.1 Specify Log4j config file: there is now a command-line switch (-log4jconfig) to specify the Log4j configuration file. Importantly, this can be either in the .properties format or the .xml format. The .xml format is more verbose (no surprise) but also allows more configuration options. From the Log4j tutorial: "The properties file does not support some advanced configuration options like Filters, custom ErrorHandlers and a special type of appenders, i.e. AsyncAppender. ErrorHandlers defines how errors in log4j itself are handled, for example badly configured appenders. Filters are more interesting. From the available filters, I think that the level range filter is really missing for property files." In addition to these change there quite a few little hygiene cleanups that made me happy.

 

W3C link checker    Powered by Movable Type 3.16
This weblog is licensed under a Creative Commons License.
Agitar, Agitator, Software Agitation, Open Quality, and Quality Level Agreement are trademarks of Agitar Software, Inc.

Terms of Use