On 08.01.24 20:42, OCsite wrote:
[...]> - the extension class list is collected compile-time and (eventually
when my build script creates the application) automatically added to the
/org.codehaus.groovy.runtime.ExtensionModule/ manifest, so that they
just-work without any extra ado.
So your
Jochen,
> On 8. 1. 2024, at 16:10, Jochen Theodorou wrote:
> I would like to know from users on this list mostly if they are using
> specific features of the meta class system and MOP, but especially what for.
>
> (1) categories
> ...
> use (CategoryClass) {
> // some code and callstack here
I myself use @POJO almost everywhere.
On Mon, Jan 8, 2024, 09:11 Jochen Theodorou wrote:
> Hi all,
>
> I would like to know from users on this list mostly if they are using
> specific features of the meta class system and MOP, but especially what
> for.
>
>
> (1) categories
>
>
Hi all,
I would like to know from users on this list mostly if they are using
specific features of the meta class system and MOP, but especially what for.
(1) categories
https://blog.mrhaki.com/2009/09/groovy-goodness-use-categories-to-add.html
shows an example. Basically you have
use
Hello Paul!
That explains all the - at least to me - strange behavior.
I also saw in the doc Bob pointed me to that there is a grape resolve command
to check the transitive dependencies of a grape.
So no need to set up a dummy script for this and delete the ~/.groovy/grapes
directory and
If you look up the Javadoc for Grab, you will see that it can be on
more things than just an import. It can be on a type, a method, a
field, a local variable and so forth. It can't be used on a single
statement. The suggestion for placing it on an import statement is
really just a suggestion. It
