Do you mean make a fork on GitHub? And then submit a failing test in the fork?
I guess I have two issues with that recommendation: a) I am not sure how you would test this, as I am doing everything via shell. In fact, given that a failed build doesn't return 0, what I submitted is a failed test. It doesn't clean up afterwards, however, and I don't know how to hook it into the build/test system. b) I was kind of hoping I wouldn't need to read how the plugin system works, and download all the plugins, and build gradle and the plugins, and...well, become a plugin expert. I suppose eventually I will get to the point of writing my own Gradle plugin, and then b) is right around the corner. ;-) But thanks for all the great work. I like Gradle a lot, and am enjoying using it, minor hiccups and all. Strayph On Jun 9, 2011, at 4:16 PM, Peter Niederwieser [via Gradle] wrote: > strayph wrote: > Also, no one is yet assigned to the JIRA. > > Has anyone looked at it yet? Do I need to update it somehow to make it more > shnazzy? > > I think it will be an easy fix. > > Strayph > The best way to get in a fix really fast is to submit a pull request on > GitHub, along with a test. > > -- > Peter Niederwieser > Principal Engineer, Gradleware > http://gradleware.com > Creator, Spock Framework > http://spockframework.org > Blog: http://pniederw.wordpress.com > Twitter: @pniederw > > > If you reply to this email, your message will be added to the discussion > below: > http://gradle.1045684.n5.nabble.com/Plugin-Conflict-war-and-eclipse-fail-with-compile-fileTree-tp4463299p4474587.html > To unsubscribe from Plugin Conflict: 'war' and 'eclipse' fail with compile > fileTree, click here. -- View this message in context: http://gradle.1045684.n5.nabble.com/Plugin-Conflict-war-and-eclipse-fail-with-compile-fileTree-tp4463299p4474640.html Sent from the gradle-user mailing list archive at Nabble.com.
