logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-595) Support plugin preloading through the standard javax.annotation.processing tool
Date Sat, 05 Apr 2014 20:38:15 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961229#comment-13961229

Ralph Goers commented on LOG4J2-595:

A "typical" user of log4j should only need log4j-api and log4j-core and no other dependencies.
 I consider a typical user to be one who creates their own plugins and who may or may not
preload them.  

We have added a lot of dependencies, such as the disruptor, and I am not entirely sure if
they are optional or not. But adding more jars is going in the wrong direction.

There are two ways to address this issue that I see:
1. Create a maven plugin to replace the exec plugin.
2. Create an annotation processor for the compiler to use. If you want to put just the annotation
processor in its own jar that would be OK. We would have to tell Maven users to use provided
scope to keep Maven from including it when it packages.

> 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

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message