Qi4j community migrated away from Maven after several years of frustration, especially around release management, versioning and cross-module dependency resolution issues, in Feb 2011. The tool of choice is now Gradle, and it doesn't require any installation, there are gradlew and gradlew.bat in the root folder of the Qi4j SDK that will bootstrap Gradle if not done so already.Gradle is very flexible, and we have defined (or in the process of defining) the following tasks (same as Ant's targets).
clean
Clean up of all build output and restoring the code base to a fresh state.build
This is the default build, which creates the jars, runs checkstyle and tests with cobertura, and produces test coverage reports in the qi4j-sdk/build/reports directory.regression
Runs the Regression TestsperfTest
Runs the Performance Tests.javadocs
Produces the Javadocs for the code base. The full javadoc is placed in qi4j-sdk/build/javadocs, and the generation is supposed to be grouped in a nice natural way.dist
Creates the release output into the qi4j-sdk/build/distributions directory.publish
Uploads the release artifacts to the distribution servers, such as http://repository.ops4j.org/maven2 and http://www.qi4j.org website.