When I reinstalled (as Peter suggested), I noticed that the stacktrace was
different the first time than each subsequent time, which reminded me that I
was using the --daemon option.  Omitting that option, I now get this
consistently:

org.gradle.api.tasks.TaskExecutionException:  Execution failed for task
':compileGroovy'.
         at org.gradle
.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:71)
         ...many more lines...
Caused by java.lang.NoClassDefFoundError: org/objectweb/asm/Opcodes
         at org.gradle.api.AntBuilder.<init>(AntBuilder.java:23)
         ...many more lines...

Notice that though the stacktrace is almost the same as before, the message
of the NoClassDefFoundError is different.  Does this shed any light on this
problem for any of you (unfortunately, it doesn't for me)?

Thanks in advance!
Mark

On Sat, Jun 4, 2011 at 4:50 PM, Mark Drew <[email protected]> wrote:

> I just installed it, but I can try reinstalling it on Monday.
>
> Thanks!
> Mark
>
>
>
> On Fri, Jun 3, 2011 at 6:14 PM, Peter Niederwieser <[email protected]>wrote:
>
>>
>> Mark Drew wrote:
>> >
>> > I have a Groovy project that builds just fine on one machine.  However,
>> I
>> > just moved it to another machine, and now the :compileGroovy task fails.
>> > The cause listed is
>> >
>> > Could not initialize class org.codehaus.groovy.runtime.InvokerHelper
>> >
>>
>> Have you tried to reinstall Gradle? Maybe the current installation got
>> tampered with.
>>
>> --
>> Peter Niederwieser
>> Principal Engineer, Gradleware
>> http://gradleware.com
>> Creator, Spock Framework
>> http://spockframework.org
>> Blog: http://pniederw.wordpress.com
>> Twitter: @pniederw
>>
>>
>>
>> --
>> View this message in context:
>> http://gradle.1045684.n5.nabble.com/Could-not-initialize-class-org-codehause-groovy-runtime-InvokerHelper-tp4452034p4452722.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
>>
>>
>>
>

Reply via email to