@maxonfjvipon Please review

@yegor256 please check

@levBagryansky just setting it to public is not a solution. We should introduce a test first, which will fail if public is not there. Then, we make a fix.

@levBagryansky isn't it easier to use Reflection for this, in runtime? When unit tests in the eo-runtime package are executed, all Java classes are parsed and available in classpath. Just search for all classes in the package and check their access modifiers.

@yegor256 I tried to use Dataized in this script and get the error

[ERROR] /home/tardis3/eo/eo-runtime/src/test/groovy/check-eo-classes-are-public.groovy: 29: unable to resolve class org.eolang.Dataized
[ERROR]  @ line 29, column 1.
[ERROR]    import org.eolang.Dataized
[ERROR]   

Looks like the main issue is how to use foreign dependencies in groovy-maven-plugin

@levBagryansky that's what I'm saying. You don't need Groovy for this task. Just create a normal unit test in the eo-runtime: it should scan the classpath, find all classes in the EOorg.EOeolang package, and check their access modifiers (through reflection). Should be easy. Most probably you should use this lib: https://github.com/ronmamo/reflections

@yegor256 please check. For some reason reflections did not counted all classes, so I used guava here. Here we check 827 classes

@yegor256 please check

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 17min)