On Wed, 2009-04-01 at 13:53 +0200, Tom Eyckmans wrote: > 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?
OK, I'll do the n00b thing: why is buildSrc involved?
Of course I have made changes to the build.gradle file for this project,
and now I cannot reproduce the error. It sort of makes progressing this
a) hard; and b) pointless?
> 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.
In this particular case the summary report is:
Cause: org/objectweb/asm/Opcodes
where the fuller expression of this is:
Caused by: java.lang.NoClassDefFoundError: org/objectweb/asm/Opcodes
I wonder if an immediate expediant is to change the way the summary is
reported so as to give the exception name. In this case it says it all
-- for a programmer anyway.
--
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]
London SW11 1EN, UK. m: +44 7770 465 077 xmpp: [email protected]
signature.asc
Description: This is a digitally signed message part
