> I must say, as graciously as possible, WTF? Nothing scary :) It's just the 'eclipseConfigurer' task went away some time ago I wanted to know what's the behavior with the latest trunk.
Could be a bug. Can you file a jira issue and attach the full stack trace? Cheers! On Wed, Jun 8, 2011 at 1:10 AM, strayph <[email protected]> wrote: > Okay, this is pretty weird. > > I upgraded to milestone-3, and get the exact same type of error, but in a > different task: > milestone-2 => Execution failed for task ':eclipseConfigurer'. > milestone-3 => Execution failed for task ':eclipseWtpComponent'. > > I must say, as graciously as possible, WTF? > > Strayph > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Plugin-Conflict-war-and-eclipse-fail-with-compile-fileTree-tp4463299p4463366.html > Sent from the gradle-user mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Szczepan Faber Principal engineer@gradleware Lead@mockito --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
