Move logging configurations into package-specific resources
Basics
Logistics
Basics
Logistics
Description
As in MDA-256:
Logback complains if configurations appear more than once in the classpath, for example because they are supplied in the same location in more than one JAR.
Note that such a situation is in any case invalid under the rules of the module system: it corresponds to a split package.
To avoid any possibility of this, the CLI package should not define its configuration resources in the default package, but in its own package where they are guaranteed not to clash with resources from other JARs.
I'm going to do first, so we can probably steal the code from there.
As in MDA-256:
Logback complains if configurations appear more than once in the classpath, for example because they are supplied in the same location in more than one JAR.
Note that such a situation is in any case invalid under the rules of the module system: it corresponds to a split package.
To avoid any possibility of this, the CLI package should not define its configuration resources in the default package, but in its own package where they are guaranteed not to clash with resources from other JARs.
I'm going to do first, so we can probably steal the code from there.