[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-dev
Subject:    [jira] [Commented] (LOG4J2-741) Reinstate the package attribute for discovering custom plugins
From:       "Matt Sicker (JIRA)" <jira () apache ! org>
Date:       2014-07-29 19:24:39
Message-ID: JIRA.12729465.1406210793531.68255.1406661879564 () arcas
[Download RAW message or body]


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

Matt Sicker commented on LOG4J2-741:
------------------------------------

The way that plugins are registered through OSGi is done at install time for each \
bundle. It's not repeated unless you refresh the bundle for instance, and that \
requires restarting everything as it is.

> Reinstate the package attribute for discovering custom plugins
> --------------------------------------------------------------
> 
> Key: LOG4J2-741
> URL: https://issues.apache.org/jira/browse/LOG4J2-741
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0, 2.0-rc2
> Reporter: Remko Popma
> Assignee: Remko Popma
> Priority: Blocker
> Fix For: 2.0.1
> 
> Attachments: LOG4J2-741-patch.txt
> 
> 
> Several people reported problems with their custom plugins no longer being \
> recognized by log4j2. See LOG4J2-673 and [this StackOverflow \
> question|http://stackoverflow.com/questions/24918810/log4j2-configuration-will-not-load-custom-pattern-converter].
>  Plugins created before the annotation processor was added to log4j2 (all plugins \
> created with 2.0-rc1 and earlier) may not have a \
> {{META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat}} file. \
> Previously plugins without this metadata file could still be found if the user \
> specified their custom plugin package(s) in the {{packages}} attribute of the \
> {{<Configuration>}} element in their log4j2.xml configuration file. However, since \
> 2.0-rc2, the {{packages}} configuration attribute was disabled; users may still \
> specify a value, but log4j2 will no longer use this value to try to load custom \
> plugins. This causes problems for custom plugins built before the annotation \
> processor was added to log4j2, as well as custom plugins that are built in an \
> environment where the annotation processor does not work (for example, most IDEs \
> require some setting changes to enable annotation processing). This Jira ticket is \
> to reactivate the packages configuration attribute. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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


[prev in list] [next in list] [prev in thread] [next in thread]