[
https://issues.apache.org/jira/browse/LOG4J2-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961230#comment-13961230
]
Matt Sicker commented on LOG4J2-595:
------------------------------------
Right now I'm just including it in log4j-core so we can use it ourselves,
though I'm not entirely sure if an annotation processor can be run on the same
module it's in (and splitting it into its own module would introduce a circular
dependency with log4j-core if the annotations weren't also split out). I'm also
creating a serializable object that corresponds to a plugin entry in the .dat
file for easier reading/writing.
> Support plugin preloading through the standard javax.annotation.processing
> tool
> -------------------------------------------------------------------------------
>
> Key: LOG4J2-595
> URL: https://issues.apache.org/jira/browse/LOG4J2-595
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0-rc2
> Environment: Recent versions of Java and Maven
> Reporter: Matt Sicker
> Labels: annotations, compiler, plugins
> Attachments: Move_plugin_annotations_to_their_own_module_.patch
>
>
> Currently, in order to preload plugins, you have to add an exec-maven-plugin
> task to scan your code. Ideally, there'd be an annotations artifact (at least
> for the plugin annotations, but really just has to have all the necessary
> ones used for this) and a processor artifact that you'd include in your
> project. Then the maven-compiler-plugin would automatically run that
> annotation processor on your project during the compile phase. This would
> require less work from the end user to support their own custom plugins.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
