[
https://issues.apache.org/jira/browse/LOG4J2-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037465#comment-14037465
]
Mck SembWever edited comment on LOG4J2-595 at 6/19/14 4:12 PM:
---------------------------------------------------------------
from src/site/xdoc/manual/plugins.xml
{quote}
Annotated classes marked with <code>@Plugin</code> or
<code>@PluginAliases</code> are now automatically preloaded when you include
the log4j-core artifact.
{quote}
This isn't the case for my own plugin…
was (Author: michaelsembwever):
where's the documentation for this?
src/site/xdoc/manual/plugins.xml in trunk remains outdated.
(and can't get my own plugin working)
> 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
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
