Issue Created: http://issues.gradle.org/browse/GRADLE-1548
I've also tested this with the master branch of Gradle (I assume that's always going to be the most current?) - Andrew On Thu, May 12, 2011 at 10:41 PM, Szczepan Faber <[email protected]> wrote: >>Should I raise a JIRA about this? > Yes, please. >>With M3, it explodes because it can't find the source JARs > We had similar problem recently in our build. Would you mind trying out > today's snapshot and running gradle eclipse? > distributionUrl=http\://repo.gradle.org/gradle/distributions/gradle-snapshots/gradle-1.0-milestone-4-20110512131549+1000-bin.zip > Thanks a bunch! > Szczepan > On Thu, May 12, 2011 at 12:23 PM, Andrew Thorburn <[email protected]> wrote: >> >> Ok, it appears to be a regression in Milestone 3, not with the Eclipse >> Plugin. With M1, 'gradle eclipse' runs without errors. With M3, it >> explodes because it can't find the source JARs (but it definitely >> finds the class file JARs, looking at the debug output). Should I >> raise a JIRA about this? >> >> A quick look at the breaking changes for Milestone 2 / 3 don't >> indicate any areas I would have thought would break this. >> >> - Andrew >> >> On Thu, May 12, 2011 at 10:01 PM, Szczepan Faber <[email protected]> >> wrote: >> > Hey >> > >> >> On reflection, I haven't tried building it on the command line with >> >> Milestone 3, only Milestone 1, so it's possible there are breaking >> >> changes introduced there that are the cause of this. >> > >> > That's a good idea. Also, does 'gradle eclipse' task work for you fine? >> > Cheers, >> > Szczepan >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
