Charles Oliver Nutter schrieb:
> Jochen Theodorou wrote:
>> hmm... I am currently asking myself if we need to resolve the classes
>> we create when we compile. I know I had once a strange problem with
>> this, but I think that was with the ReflectorLoader, which is very
>> special anyway.
>>
>> hmm... the build seems to be ok with that change...
>
> You shouldn't need to resolve them. JRuby's compiler just leaves them as
> byte[] and dumps them to disk without ever loading them.
depends on the usage, or not? The normal mode in groovy is to not to
write them to disc, so I think there are some differences to Ruby here.
Anyway, I removed the call to resolveClass, normally the problem should
go away now, unless the plugin loads the classes at some point.
hmm... which might happen, when the next compilation step is done... I
am not sure. It is really bad, that a classloader does not allow us to
ask for a class without loading it...
bye blackdrag
--
Jochen "blackdrag" Theodorou
Groovy Tech Lead (
http://groovy.codehaus.org)
http://blackdragsview.blogspot.com/---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
