log4j.jar version conflict
Parts of my plug-in's code depend on log4j, but a newer version than IDEA is
using. Currently, I can work-around this problem by removing the log4.jar
from the IDEA SDK and use my own. I have not tried running/debugging my
plug-in, but I guess it will fail. Do you plan to turn IDEA's plugin
architecture into some kind of OSGi framework?
Tom
Please sign in to leave a comment.
ping
FWIW
If I recall the last released version of log4j brought in several new dependencies, I am assuming you are using those new features ?
-Rob
No, I'm not aware of some dependencies. We just make use of the additional
trace level.
Tom
Hello Tom,
No, we don't have any such plans for version 9. Can't the problem be solved
by simply upgrading our bundled log4j?
--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"
Hello, Dmitry!
I start writing plugin for documentum. Documentum primary library is DFC (documentum foundation classes), which depends on log4j
(Implementation-Version: 1.2.13 accorfing to Manifest in attached jar)
When I try to perform simple action calling dfc methods in plugin development enviroment, it produce error:
Exception in thread "main" java.lang.NoSuchMethodError: org.apache.log4j.spi.LoggingEvent.getLevel()Lorg/apache/log4j/Level;
at com.documentum.fc.tracing.impl.TraceItem.getMessage(TraceItem.java:176)
How I can avoid this problem in graceful manner? I want write plugin for sharing with community without modification of primary IDEA files/libraries.
Attachment(s):
log4j.jar
any news?