It seems as though the Codehaus Mojo Project has reached the end of the line.  After finishing up my testdox maven plugin, I tried to contribute my plugin to the Codehaus Project, but it has fallen on deaf ears.  I guess it’s time to take things into my own hands, and so I’m happy to announce the first official release of the testdox maven plugin.

Enabling the plugin is a snap.  Just add this xml block to your maven2 project and the next time you build your site documentation, the superfancy testdox report will be included in your project reports.

<repositories>
  <repository>
    <id>codecrate-repository</id>
    <name>Codecrate Repository</name>
    <url>http://maven.codecrate.com/</url>
  </repository>
</repositories>

<reporting>
  <plugins>
    <plugin>
      <groupId>com.codecrate.maven.plugins</groupId>
      <artifactId>testdox-maven-plugin</artifactId>
    </plugin>
  </plugins>
</reporting>

Just incase you’ve missed out on my previous blogentries, the testdox report creates a human readable HTML report of your JUnit test suites.  Try it out today, and let me know what you think!

It’s unfortunate that the Codehaus Mojo project is in the state that it is.  Since the Maven core codebase is ASF licensed, non-ASF contributions can not be included in the Maven core.  That makes this this extension project extremely important to encourage users to develop plugins for the “rest of the non-ASF” world.

This is exactly why the wicket-stuff project is such an important partner to the core wicket project.  And wicket-stuff is definitely doing things right. Tons of contributions and an extremely low barrier for new projects to get up and running.