Move logging configurations into package-specific resources
Basics
Logistics
Basics
Logistics
Description
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 module should not define its configuration resources in the default package, but in the net.shibboleth.metadata.cli package where they are guaranteed not to clash with resources from other JARs.
The same comment, of course, applies to the corresponding resources in other projects. In this case, the clash is with the logging resources for the abstract CLI utility class in spring-extensions, and I will raise another ticket there.
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 module should not define its configuration resources in the default package, but in the
net.shibboleth.metadata.clipackage where they are guaranteed not to clash with resources from other JARs.The same comment, of course, applies to the corresponding resources in other projects. In this case, the clash is with the logging resources for the abstract CLI utility class in
spring-extensions, and I will raise another ticket there.