On 28.11.2015 10:25, Cédric Champeau wrote:
Modules can export internals to Groovy, thanks to the concept of
"automatic modules". However, the automatic modules are inferred from
the jar name. Which is a weak strategy, but honestly I can't find any
better solution. So for groovy, since we have multiple flavors, this is
a problem. Because we have groovy-all, groovy, and all individual
modules. That's just a nightmare.

BTW, I recommend that everybody interested in this topic takes an hour
to see this talk from Mark Reinholds:
https://www.youtube.com/watch?v=UKC0uC7QUkI

ah right, I messed up a little... the unnamed module is for classes without jar... for example our runtime generated scripts.

bye blackdrag

Reply via email to