| Re: [m2e-users] Maven Console log is blank |
|
The bug is „fixed“ through installing the m2e logback feature into the DSL package, which changes the load order of the slf4j bindings, so the
logback backend is initialized before the log4j12 backend shipped by egit. Maybe someone needs to convince the egit developers to not depend on the slf4j-log4j12 backend? I’ll try to get the discussion started… Von: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx]
Im Auftrag von Eric B Thanks! Indeed, it is the same bug. I saw that your bug has been fixed, but I'm not sure where/how to get the fix from. I'm not using the DSL package, but I get the same errors with EGit 4.1.1.201511131810-r
installed on my WTP installation. Were you able to download a pkg fix, or are you still working with your manual bundles.info patch? Thanks,
On Mon, Jan 11, 2016 at 7:10 AM, Tobias Gruetzmacher <Tobias.Gruetzmacher@xxxxxxxxxxxxxxxxxxx> wrote: This is probably the same (or a similar) problem as I reported in
https://bugs.eclipse.org/bugs/show_bug.cgi?id=482600 Von:
m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx]
Im Auftrag von Eric B Hi, I have a fairly new installation of Juno in which I added m2e 1.4.1 and m2e-slf4j over logback. Both installed without errors. And yet, when I open my Maven Console, it is blank. No output at all. I've tried editing the .metatdata/.plugins/org.eclipse.m2e.logback.configuration/logback.***.xml file to set the root level to DEBUG, but no difference. I suspect I might be missing something critical in Eclipse itself (or an incorrect logback config), but not entirely sure where to look. Does anyone have suggestions where/how I can debug this problem?
|