logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Sicker (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (LOG4J2-595) Support plugin preloading through the standard javax.annotation.processing tool
Date Sun, 20 Jul 2014 02:22:38 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Matt Sicker closed LOG4J2-595.

> 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
>            Assignee: Matt Sicker
>              Labels: annotations, compiler, plugins
>             Fix For: 2.0-rc2
> 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