-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Generate Log4jPlugins
class does not compile in JPMS
#3251
Comments
A workaround for this issue is to add: <dependency>
<groupId>biz.aQute.bnd</groupId>
<artifactId>biz.aQute.bnd.annotation</artifactId>
<version>7.1.0</version>
<scope>provided</scope>
</dependency> to the compile-time only classpath and a: requires static biz.aQute.bnd.annotation; to the module descriptor. The annotations have a |
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
Just wanted to confirm -- the suggested workaround code changes on the source -- not during usage, correct? Meaning... wait until beta4 to use the PlugProcessor in non-OSGi environments |
|
@ppkarwasz to clarify my use case -- I was attempting to build a a custom plug however the annotation processor (using Kotlin Kapt) breaks -- complaining that the annotations are unable to be resolved. And tasks for the prompt feedback
|
Did you try adding: compileOnly 'biz.aQute.bnd:biz.aQute.bnd.annotation:7.1.0' to your dependencies? |
Yes -- that does solve the issue -- thanks |
Currently
log4j-plugin-processor
in version3.0.0-beta3
of Log4j Core adds BND annotations to the generated code.While these might be useful for OSGi users, they cause a compilation error if the
biz.aQute.bnd.annotation
module is not present:static
dependency on the module is not declared in themodule-info.java
file.The text was updated successfully, but these errors were encountered: