JIRA Issue: KIEKER-1750 Allow Kieker to be used in the module path
Original Reporter: Nils Christian Ehmke
Currently it is not possible to use Kieker in the module path. The Kieker Jar contains classes from various non-kieker packages (org.apache.commons, jctools, ...). This leads to serious problems when used with the Jigsaw module system. Java detects that the same package is exported from two different modules. This is not allowed. You will get an error message like
Error occurred during initialization of boot layer
java.lang.module.ResolutionException: Modules commons.logging and kieker export package org.apache.commons.logging.impl to module slf4j.api
JIRA Issue: KIEKER-1750 Allow Kieker to be used in the module path Original Reporter: Nils Christian Ehmke
Currently it is not possible to use Kieker in the module path. The Kieker Jar contains classes from various non-kieker packages (org.apache.commons, jctools, ...). This leads to serious problems when used with the Jigsaw module system. Java detects that the same package is exported from two different modules. This is not allowed. You will get an error message like
Error occurred during initialization of boot layer java.lang.module.ResolutionException: Modules commons.logging and kieker export package org.apache.commons.logging.impl to module slf4j.api