|
|
|
|
Re: Error with log4j [message #686136 is a reply to message #669951] |
Sun, 19 June 2011 22:10 |
docere@gmail.com Messages: 1 Registered: July 2010 |
Junior Member |
|
|
Not sure if this will help, but I just got out of that problem by
creating a new work space directory and reimporting (with copying set to
true) my projects from my old workspace.
Every once in a while, the eclipse cache of plugins goes out of synch
within the workspace creating all kinds of bizarre errors in plugin
related development.
By recreating your the workspace through this importing process, these
errors go away.
Hope that helps,
Arnold
On 5/12/2011 3:42 AM, Christophe Jouvray wrote:
> In another post, I saw this issue, so I already checked if
> SL4J is installed. That's not the case.
> Anything else to check?
>
> I searched all plugins related to logging, and I obtain the
> following list:
> org.apache.commons.logging (1.0.4.v201005080501) "Apache
> Commons Logging Plug-in" [Resolved]
> org.apache.commons.logging (1.1.1.v201005080502) "Apache
> Commons Logging Plug-in" [Resolved]
> org.apache.log4j (1.2.15.v201005080500) "Apache Jakarta
> log4j Plug-in" [Resolved]
> org.eclipse.papyrus.log (0.7.2.v201101191114) "Papyrus
> Logging plugin(Incubation)" [Active]
> org.eclipse.ui.views.log (1.0.100.v20110210_r362) "Log View"
> [Active]
> org.eclipse.xtext.logging (1.2.15) "Xtext log4j fragment"
> [Resolved]
>
> I don't know the difference between Active and Resolved. So,
> I don't know if Resolved for log4j is annoying or not.
>
> Thank you for your help!
|
|
|
|
Powered by
FUDForum. Page generated in 0.04019 seconds