Ant 1.7 gibt’s ja schon gefühlte ewige Zeit und bei Ant, dem make des 2.0 Zeitalters, steht ein Update ein. Nichts großes, sondern eher Detailverbesserungen:

Apache Ant 1.8.0RC1 is now available for download .

• a new top level element extension-point allows build files to be extended with custom targets more easily
• if and unless attributes will be evaluated according to the values of the properties entered if these properties evaluate to true, false, on, off
• Ant now requires Java 1.4 or later
• new task include provides an alternative to <import> that should be preferred when you don’t want to override any targets
• numerous bug fixes and improvements as documented in Bugzilla and in WHATSNEW

While in open source projects a final release date strongly depends on the free time of the volunteers/committers, the final release is expected one to two months maximum after this RC. So Ant 1.8.0 is expected between mid February and mid March 2010.

Von der http://code.google.com/p/googleappengine/ gibt’s eine neue Version. Die Neuerungen in kürze:

• Support for JAXB. JAXB is included in JDK 1.6 (and App Engine’s production servers). If you’re using JDK 1.5 with your local dev_appserver, you will need to include the JAXB libraries with your application to use it.
  • http://code.google.com/p/googleappengine/issues/detail?id=1267
• New support for application pre-compilation to reduce the length of loading requests. To enable pre-compilation on your application, add this flag to your appengine-web.xml:
  • <precompilation-enabled>true</precompilation-enabled>
  • If you have trouble deploying your application, you should remove this flag or set it to false.
• Added Quota API (com.google.appengine.api.quota) to match Python
• Low-level Memcache API now supports incrementAll()
• HTTPResponse object now has getFinalUrl() method for 302 redirects.
  • http://code.google.com/p/googleappengine/issues/detail?id=1464
• Java Dev Appserver now automatically executes tasks. If you prefer the old behavior where tasks do not automatically execute you can use the –jvm_flag=-Dtask_queue.disable_auto_task_execution flag when starting the server.
• Additional file extensions permitted when sending mail.
  • http://code.google.com/p/googleappengine/issues/detail?id=494
• Fixed issue with Java mail handler not processing multipart messages correctly
• Fixed agent code included in appengine-local-runtime.jar results in RuntimeException
  • http://code.google.com/p/googleappengine/issues/detail?id=2280
• Fixed issue with sort orders defined on properties that allow multiple values
  • http://code.google.com/p/googleappengine/issues/detail?id=2349
• Fixed problem with dropped query strings after requiring log-in
  • http://code.google.com/p/googleappengine/issues/detail?id=2225
• Removed limitation preventing multiple parameters with the same name
  • http://code.google.com/p/googleappengine/issues/detail?id=2090
• Fixed issue with local datastore incorrectly sorting results of ancestor queries
  • http://code.google.com/p/googleappengine/issues/detail?id=2177

Vom Quellcode-Checker Checkstyle gibt es eine neue Version 5. Die Änderungen beschreiben die Seite http://checkstyle.sourceforge.net/releasenotes.html.

The following checks were added since release 4.4:

• AnnotationUseStyle
• MissingDeprecated
• MissingOverride
• PackageAnnotation
• SuppressWarnings
• EqualsAvoidNull
• NoClone
• NoFinalizer
• AvoidStaticImport
• JavadocPackage
• ClassTypeParameterName
• MethodTypeParameterName
• RegexpMultiline
• RegexpSingleline
• RegexpSinglelineJava
• OuterTypeNumber
• FileTabCharacter
• GenericWhitespace

Die Infos gibt es unter http://kentbeck.github.com/junit/doc/ReleaseNotes4.8.html. Die Änderungen halten sich in Grenzen:

Summary of Changes in version 4.8

Categories

From a given set of test classes, the Categories runner runs only the classes and methods that are annotated with either the category given with the @IncludeCategory annotation, or a subtype of that category. Either classes or interfaces can be used as categories. Subtyping works, so if you say @IncludeCategory(SuperClass.class), a test marked @Category({SubClass.class}) will be run.

You can also exclude categories by using the @ExcludeCategory annotation

Example:

public interface FastTests { /* category marker */ }
public interface SlowTests { /* category marker */ }

public static class A {
    @Test
    public void a() {
        fail();
    }

    @Category(SlowTests.class)
    @Test
    public void b() {
    }
}

@Category({SlowTests.class, FastTests.class})
public static class B {
    @Test
    public void c() {

    }
}

@RunWith(Categories.class)
@IncludeCategory(SlowTests.class)
@SuiteClasses( { A.class, B.class }) // Note that Categories is a kind of Suite
public static class SlowTestSuite {
  // Will run A.b and B.c, but not A.a
}

@RunWith(Categories.class)
@IncludeCategory(SlowTests.class)
@ExcludeCategory(FastTests.class)
@SuiteClasses( { A.class, B.class }) // Note that Categories is a kind of Suite
public static class SlowTestSuite {
  // Will run A.b, but not A.a or B.c
}

Bug fixes

• github#16: thread safety of Result counting