[
https://issues.apache.org/jira/browse/LOG4J2-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868701#comment-13868701
]
Ralph Goers commented on LOG4J2-162:
------------------------------------
I don't believe it will be. Our OSGi support is still incomplete but I doubt
we will ever be able to support older versions well.
> 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
> Attachments: log4j-PluginManager-FrameworkUtil-stacktrace.txt
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
