Status of the 1.0 release
We are working intensely towards the 1.0 release. The remaining work is focused on the new dependency cache, the daemon and performance tuning. We will also continue to fix bugs in various other areas.
The new dependency cache
We are very excited about our new dependency cache. It solves many fundamental issues that current repository based builds have, whether their build system is Ant + Ivy, Gradle, SBT, Buildr, Leiningen or Maven. To learn more about it, see: http://t.co/R4Vt9SSu
We considered it crucial to have these improvements in 1.0. The road to the new cache has been a little bit more bumpy than we expected . Some bugs in the new dependency cache caused severe regressions in our now-rescinded 1.0-M4 release.
Once the major issues with the new cache are fixed, we will release gradle 1.0-m5.
The daemon is crucial to make Gradle a highly responsive build system. The startup and initialization time of any of the new major JVM languages is significant. As Gradle is based on Groovy, it is also suffering those delays. The solution to this is the Gradle daemon which provides a long running pre-initialized JVM to avoid the startup time. Having a long running Gradle agent will give us a tool to do many more optimizations in the future (e.g. pre-fetching snapshot dependencies). For now, we need to make it production ready. You can already opt-in to have the daemon enabledvia the –daemon flag at the CLI or in the GRADLE_OPTS environment variable. Several Gradleware team members and I have worked with this option enabled for the last 6 months. But you might run sometimes into issues such as with file-locks under Windows. Then you have to manually kill the daemon process.
Once the remaining daemon issues are fixed we will release gradle 1.0-beta-1
We are tackling performance issues continuously and there will be still performance optimizations we want to do after 1.0-beta-1 is released. Therefore although 1.0-beta-1 will be feature complete, we don’t want to call it a release candidate as we still have plans to modify code for performance optimizations. Performance is very important to the Gradle team. Gradle has excellent performance in many areas. But there are some areas where we still have a lot of potential for improvement.
Once we are done with the performance improvements, we will release gradle 1.0-rc-1.