Hans, Because I thought the rest of my build logic was messing up with gradle 0.6.1 i just created a test project on the side. All its build.gradle file contains is the usePlugin line. So its a single line build script with one hello world class file in src/main/java.
Hope this helps, and btw, we've been very happy with Gradle on our project after trying gant and other alternatives. We use it for the main build, bamboo integration, and even putting together mySql initialization scripts and pushing those to the database right before the tests happen. The 0.6 version looks like it fixes some of the quirks we had to put in to our build script and is the main reason why I was trying to upgrade :) - Gennadiy On Thu, Jun 4, 2009 at 3:33 AM, Hans Dockter <[email protected]> wrote: > > On Jun 3, 2009, at 8:53 PM, Gennadiy Shafranovich wrote: > > I am trying to upgrade an existing project that was built with Gradle >> 0.5.2 to 0.6.1. Our install of 0.5.2 is using the embedded groovy jar from >> version 1.6.2 instead of the one it was distributed with to get a few more >> useful functions. It was running fine. I tried upgrading and ran into major >> issues. >> >> I traced these down and set up a simple build.gradle script on a test >> project with just one line: >> >> usePlugin('java') >> >> I get the following output from gradle: >> >> Build failed with an exception. >> Run with -s or -d option to get more details. Run with -f option to get >> the full (very verbose) stacktrace. >> >> Build file >> '/home/gshafranovich/eclipse-workspaces/test/build/build.gradle' line: 1 >> >> A problem occurred evaluating root project 'build'. >> Cause: >> org.codehaus.groovy.reflection.CachedClass.getCachedClass()Ljava/lang/Class; >> >> BUILD FAILED >> >> I think this is because the return type of CachedClass.getCachedClass() >> has changed from java.lang.Class to CachedClass in groovy 1.6.2. >> >> I am going to hold off on upgrading until Gradle would be compatible with >> a later version of groovy. Does anyone have any suggestions on whether my >> assumption are correct or not? >> > > It would be very helpful to see the buildscript. Or at least the parts > where the plugin and the dependencies are declared. > > - Hans > > -- > Hans Dockter > Gradle Project Manager > http://www.gradle.org > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
