2009/3/24 Russel Winder <[email protected]> > Tom prompted me to be a little more detailed about the actual issue: > > Build failed with an exception. > Run with -f option to get the full (very verbose) stacktrace. > > Build file > '/home/users/russel/Repositories/Bazaar/Branches/ModeConsole/build.gradle' > > Execution failed for task ':compile'. > Cause: org/objectweb/asm/Opcodes > > Exception is: > org.gradle.api.GradleScriptException: Build file > '/home/users/russel/Repositories/Bazaar/Branches/ModeConsole/build.gradle' > Execution failed for task ':compile'. > at > org.gradle.api.internal.AbstractTask.execute(AbstractTask.java:184) > at > org.gradle.execution.DefaultTaskExecuter.executeTask(DefaultTaskExecuter.java:153) > at > org.gradle.execution.DefaultTaskExecuter.doExecute(DefaultTaskExecuter.java:144) > at > org.gradle.execution.DefaultTaskExecuter.execute(DefaultTaskExecuter.java:67) > at > org.gradle.execution.TaskNameResolvingBuildExecuter.execute(TaskNameResolvingBuildExecuter.java:88) > at org.gradle.Gradle.runInternal(Gradle.java:121) > at org.gradle.Gradle.run(Gradle.java:93) > at org.gradle.Main.execute(Main.java:229) > at org.gradle.Main.main(Main.java:79) > at org.gradle.BootstrapMain.main(BootstrapMain.java:53) > Caused by: java.lang.NoClassDefFoundError: org/objectweb/asm/Opcodes > at > org.gradle.util.GradleUtil.executeIsolatedAntScript(GradleUtil.groovy:94) > at > org.gradle.api.tasks.compile.AntGroovyc.execute(AntGroovyc.groovy:56) > at > org.gradle.api.tasks.compile.GroovyCompile.compile(GroovyCompile.java:81) > at > org.gradle.api.tasks.compile.GroovyCompile$1.execute(GroovyCompile.java:54) > at > org.gradle.api.internal.AbstractTask.doExecute(AbstractTask.java:220) > at > org.gradle.api.internal.AbstractTask.execute(AbstractTask.java:174) > ... 9 common frames omitted > Caused by: java.lang.ClassNotFoundException: > org.objectweb.asm.Opcodes > ... 15 common frames omitted > 22:42:10.240 [main] ERROR org.gradle.Main - > BUILD FAILED > > So the problem is clearly that the relevant ASM jar is not in the class > path. This means putting teh groovy jar as opposed to the groovy-all > jar as the groovy jar does not work even if unmanagedClasspath contains > all the jars from GROOVY_HOME/lib.
did you add the jars to the runtime dependencies of buildSrc? > > > This is not the real problem though, the real problem is that the error > message is very poor. The second real problem is how to deal with > getting the right jars on the right classpath. I agree that our error reporting is an area where we can improve, I'd say we always have to report buil process step + the task that failed the build (full path), we should probably also include the tasks that have already executed also when the commandline enhancements are in place. > > > I shall have to give up for now, mostly because I have to write a talk > for tomorrow evening, but also because it's late ;-) > > -- > Russel. > ============================================================ > Dr Russel Winder Partner > > Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203 > 41 Buckmaster Road, f: +44 8700 516 084 voip: > sip:[email protected] <sip%[email protected]> > London SW11 1EN, UK. m: +44 7770 465 077 xmpp: [email protected] >
