A modern programming language that makes developers happier.

kotlinlang

Now that I see this one...is there any way to use the `kotlin-spring` plugin, but be able to close some classes then "by hand" then? For instance, not all Spring beans/classes need to be "open"; an example could be a "controller" class (that doesn't feature, for instance, any `@Transactional` annotation). In that case, it's totally possible to have that just like that, but if I use `@Controller` it will be opened by default because of the `kotlin-spring` plugin.

vadimvera: no, i don’t think there’s a way for that
the “openness” of a class at compile time is based on the annotations that have been applied

Yeah, but I was wondering if there was a way I can override that by "saying" `sealed` (or something similar)...

the thing is that the plugin is integrated into the compiler itself
so it will “unseal” at compile time

If you want a more focused behavior you can use the stock `kotlin-allopen` plugin and configure it with only the annotations and meta-annotations you want.

That's a way...let me try that and see how it goes. Cheers!