Grester

The Grester project is a phenomenal Maven2 plugin that works with Jester, the JUnit tester tool. It offers a significant benefit by allowing Jester to run at any valid Maven lifecycle phase in a Maven Project. Grester provides an effortless way for developers to avoid constructing complex Java classpath entries on the commandline each time they need Jester to run against JUnit Tests in the project. Not only that, but it also helps to eliminate the need for a suite of scripts that may have been written to handle complex Java classpath executions for Maven projects.

To use Grester, you only need Maven2 installed on your system. That's it! You can start utilizing Grester's capabilities to its fullest extent without imposing any additional requirements or dependencies.

The latest release brings some exciting new changes to the project. It includes a major update to the project's groupID, changed expressly to enable the folks at codehaus.org to upload Grester to Maven's public repository. The org.apache.maven.plugins groupID is reserved for Apache folks, although it makes it more convenient to run locally without having to specify group+artifactIds.

Furthermore, Grester's documentation has also undergone significant updates. The Readme file has been modified explicitly to reflect these changes, making it simple for developers to get started with the project. These efforts aim to help newcomers understand and utilize Grester to its full capability.

Lastly, the latest version of Grester results from a feature request made on the Sourceforge.net tracker system for grester. With this update, developers can now take advantage of several new features and improvements. Grester is indeed a great tool for any developers who work with Maven2 and Jester in their projects.