If the primary constructor of a KotlinModule is called directly, bytecode compatibility problems can occur.
For this reason, this has been marked as Deprecated for quite some time.
This change raises the DeprecationLevel to error and sets the privatization schedule to 2.18.
In addition, hidden constructors and other builder functions marked as Deprecated that have long been left out for compatibility purposes are also marked for removal in 2.18.
At the same time, a hidden no-argument constructor has been added to facilitate initializing KotlinModule via reflection.
This is useful in situations where Java libraries initialize KotlinModule via reflection.
However, the Builder method of initialization is still recommended for normal use cases.
If the primary constructor of a
KotlinModuleis called directly, bytecode compatibility problems can occur. For this reason, this has been marked asDeprecatedfor quite some time.This change raises the
DeprecationLevelto error and sets the privatization schedule to 2.18. In addition, hidden constructors and other builder functions marked asDeprecatedthat have long been left out for compatibility purposes are also marked for removal in 2.18.At the same time, a hidden no-argument constructor has been added to facilitate initializing
KotlinModulevia reflection. This is useful in situations whereJavalibraries initializeKotlinModulevia reflection. However, theBuildermethod of initialization is still recommended for normal use cases.