Roadmap towards Gradle 1.0 and beyond

0.4 Release (Target date: September 10, 2008)

• Complete API documentation.
• Arbitrary multi-project layouts.
• Fine tuning of our dependency layer.
• Integration of all different kind of reports (e.g. JDepend, Checkstyle, ...) into the Java plugin (including uploading the reports).
• Further performance improvements.
• Generation of IDE files for IntelliJ, Eclipse and Netbeans. Possibly only Eclipse will make it into 0.4.

1.0 (spreaded over a couple of minor releases, Target date: End of December 2008)

• Two-phase logging (see http://www.nabble.com/2-phase-logging-to16945248.html)
• Support for ear archives.
• TestNG support
• Rich plugin system
  • classloader isolation
  • dependency declarations
  • multi-project build integration
  • running plugins from the command line against a project
  • many other features.
• Add Visitor or Listener interfaces to the core domain model where it makes sense
• Integration of Jetty for easy local testing of web applications.
• Uploading functionality for Gradle's client modules.
• Support for snapshot dependencies.
• Multi-threaded builds.
• Providing an embedded way to use Gradle.
• Allow the execution of tasks to depend on the success/failure of other tasks.

Post-1.0

• Release management
• Integration of existing ivy.xml and pom.xml files. Either by generating a Gradle build script out of them or by parsing them on the fly during a Gradle build.
• Supporting multiple languages for build scripts (e.g. JRuby, Jython)
• Distributed builds
• Source file dependency analysis for incremental builds
• Scala Plugin

Independent

• IDE plugins for IntelliJ, Eclipse and NetBeans