@yegor256, I am faced with the following problem. If we remove the prefix org.eolang from all meta +package, then the Java classes generated from EO objects will be located in target/generated-sources. Because of this, the generated classes do not have access to classes from eo-runtime/src/main/java/EOorg/EOeolang. If we move classes from eo-runtime/src/main/java/EOorg/EOeolang to eo-runtime/src/main/java (which will already be a bad practice, since some classes will be in the default-package), then to some classes that are now in the default-package, (for example, EOerror), now classes from eo-runtime/src/main/java/org/eolang (for example, PhSafe) cannot access. Of course, we can move classes from eo-runtime/src/main/java/org/eolang in eo-runtime/src/main/java, but then classes from packages (for example, EOsm/Win32/AcceptFuncCall) will not be able to access classes from eo-runtime/src/main/java. It turns out to be a vicious circle. Can you please explain what did you see the target solution?

QQ Prefix Causes Redundancy in Package Naming #4538

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions

`QQ` Prefix Causes Redundancy in Package Naming #4538