You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Greg Bowering (JIRA)" <ji...@apache.org> on 2013/02/06 07:05:12 UTC
[jira] [Created] (LOG4J2-162) PluginManager breaks for Eclipse RCP
applications using Eclipse versions older than 3.5.2
Greg Bowering created LOG4J2-162:
------------------------------------
Summary: PluginManager breaks for Eclipse RCP applications using Eclipse versions older than 3.5.2
Key: LOG4J2-162
URL: https://issues.apache.org/jira/browse/LOG4J2-162
Project: Log4j 2
Issue Type: Bug
Components: Configurators
Affects Versions: 2.0-beta3
Reporter: Greg Bowering
Priority: Trivial
My app is running under Eclipse 3.4.3 and log4j works fine so long as you don't need to locate any custom Plugins at runtime (using the configuration packages attribute) in which case ResolverUtil produces a NoSuchMethodError (see attached) for [FrameworkUtil|http://www.osgi.org/javadoc/r4v42/org/osgi/framework/FrameworkUtil.html]#getBundle(Class) which apparently is only available since Eclipse 3.5.2 (OSGI 4.2).
As a workaround I was able to run PluginManager standalone to generate org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat as described under Plugin Preloading in the manual.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org