Does this mean the Gradle team doesn't work with Eclipse and WARs and local libraries? If they do, how do they get around this problem?
I am only using the fileTree because I have an external JAR that isn't in a Maven repo, so I put it in my lib/ directory. Is there another way around this, that might allow both 'gradle war' and 'gradle eclipse' to work? Heh. Maybe I should have asked this earlier? Strayph On Jun 9, 2011, at 6:02 PM, Peter Niederwieser [via Gradle] wrote: > strayph wrote: > Do you mean make a fork on GitHub? And then submit a failing test in the > fork? > Fork the project on Github, write a JUnit or Spock test that highlights the > bug, fix the bug, and issue a pull request. If the patch is small and matches > our expectations, it will be pulled quickly. > > -- > 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-tp4463299p4474832.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-tp4463299p4475101.html Sent from the gradle-user mailing list archive at Nabble.com.
