You're right Adam. It does work for a single jar project (as expected). It might be the case I'm doing some funky with Griffon's build (due to 4 custom jar tasks) and it does not work without some manual tweaks.
Cheers, Andres ________________________________ From: Adam Murdoch <[email protected]> To: [email protected] Sent: Tue, January 18, 2011 2:37:06 AM Subject: Re: [gradle-user] Gradle 1.0 release plans On 18/01/2011, at 2:35 AM, Andres Almiray wrote: 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. > These are all excellent things to do. The main goal for Gradle 1.0 is mostly to clean up what's already there so that we can start providing some API stability. We're deferring almost everything which we can do later without breaking backwards compatibility. I'd say that all of the above would be done in some new plugins which don't exist yet, we can defer them to after 1.0. Having said that, I think a few important new features which are quick to implement will probably make it into the release. >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). > The dependencies of a project should end up in the generated pom automatically. You're not seeing this? -- Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz
