i've noticed the same - its an m2e thing.
Strange. Are there any updates or fixes planned for that? I was previously running Maven Integration for Eclipse (Required) 0.12.1.20110112-1712 org.maven.ide.eclipse.feature.feature.group with no problems. It is odd that JBoss Tools would package in a newer version of m2e with such a glaring defect.
0.12 had serious performance and memory problems and no stable API - so it wasn't like we moved to m2e 1.0 for fun
I don't have any info on this specific bug - I suggest you open one on bugs.eclipse.org and let us know the link.
(note, it might we are missing some dependency...but haven't located one yet)
Thanks for the quick response. Am not quite sure what you mean by m2e 1.0 since the version I am seeing is 0.13, but I did find this link on bugs.eclipse.org:
It seems to indicate that I need the org.eclipse.m2e.logback.feature feature installed, which I do not. However, I checked both the stable m2e update site and the m2e-extras site and neither seem to have it (they are pushing 0.12) and the new http://download.eclipse.org/technology/m2e/releasesdownload site is version 1.0. I don't see any 0.13 anywhere.
Am I comparing against the wrong version number?
I did install the m2e - slf4j over logback logging v 18.104.22.16810804-1717 plugin from that site and it seems to make a difference. I now get some logging in my maven console, although I'm not getting any DEBUG output even though I have enabled it in the Maven preferences.
But at least I have some output in the console now. Hope this helps someone else.