Hi all, Regarding gradle 1.0 being feature complete, here are a few things that I'm sure some of you have seen before but I think is good to keep in sight for 1.0 or even post 1.0
- ability to build a -sources and -javadoc jars automatically. I know this can be done with 2 tasks that take 4 lines each, but why c&p those 8 lines for every single project? - have a code-coverage plugin (based on cobertura?) that works for _all_ Test tasks defined in a build, not just the default test task. Must be able to support multiple sourceSets too. - consolidate reports and project information in a similar fashion as mvn site:site. I've spoken to a good number of maven users about migrating from mvn to gradle and they cite the lack of a site generation task one of the main reasons to hold on the switch. I believe we could come up with a site plugin that provides the behavior, the trick I think is to design a mechanism for individual tools/tasks to communicate their intention to hook up a report into the generated menu/site. One final nitpick (and this might be due to my lack of understanding of the maven plugin): dependencies must be defined manually on a generated pom (a job for a couple of LOCs but would love this to be done by convention too). Cheers, Andres ________________________________ From: Etienne Studer <[email protected]> To: [email protected] Sent: Mon, January 17, 2011 7:54:32 AM Subject: [gradle-user] Gradle 1.0 release plans Hi Adam Are there any plans, on when Gradle 1.0 will be out? Is there a certain date/quarter that you have in mind, or do you release 1.0 when the functionality is complete? If so, any rough ideas when that will be. People interested in Gradle keep asking me about it. Regards, Etienne --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
