-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Add log4j.plugin.enableBndAnnotations
option to PluginProcessor
#3258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add log4j.plugin.enableBndAnnotations
option to PluginProcessor
#3258
Conversation
This adds a `log4j.plugin.enableBndAnnotations` option to the `PluginProcessor`. Its default value is inferred from the compiler classpath. We also rename the `pluginPackage` option to a more coherent `log4j.plugin.package` option. Closes #3251
...lugin-processor/src/main/java/org/apache/logging/log4j/plugin/processor/PluginProcessor.java
Outdated
Show resolved
Hide resolved
@ppkarwasz, why do we need a toggle property instead of disabling it, always? This very much smells like leaking an internal detail through configuration properties. |
It is an option that controls the output of the |
Could you elaborate on how we can implement this? Does this also mean, there will be no need for a toggle property? |
What I mean is, I just replace: Lines 318 to 325 in e6e6ddd
with |
…processor_bnd_annotations
The processor lives in the annotation processor path, so `Class.forName` does **not** check for the presence of the BND annotation on the classpath.
This adds a
log4j.plugin.enableBndAnnotations
option to thePluginProcessor
. Its default value is inferred from the compiler classpath.We also rename the
pluginPackage
option to a more coherentlog4j.plugin.package
option.Fixes #3251