Hi all,
I was wondering about the position of other language guys on this. In
Groovy we have a command line and a runtime compilation. Now in Groovy
the command line type compilation more or less works like the runtime
version. If we compile against a class we load it by reflection do our
checks and whatever and then react accordingly. After a while we found
out how to compile here without causing an initialization... but I don'
think that is guaranteed to work like this on all VMs. Anyway... if you
now compile a Groovy program in an environment with dependency
management, like maven2, then it may be, that Groovy gets problems with
NoClassDefFound Exception because some runtime dependencies turned for
us into compile time ones.
The obvious solution to avoid that would be to to search for the jars
and look into them. Now that kind of conflicts with Groovy doing runtime
compilation. It would mean the two modes would differ substantially...
and as we know this will cause problems later on.
Having some kind of reflection with lazy Class structures would be
nice... what do others here think?
bye Jochen
--
Jochen "blackdrag" Theodorou
The Groovy Project Tech Lead (http://groovy.codehaus.org)
http://blackdragsview.blogspot.com/
--
You received this message because you are subscribed to the Google Groups "JVM
Languages" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jvm-languages?hl=en.
