Community
Participate
Working Groups
Hello committers, we received a new error report for Eclipse 4.4.0.I20140606-1215. General Information: anonymous-id: e7147c83-b264-4878-a424-3936bc4bf0f8 eclipse-build-id: 4.4.0.I20140606-1215 eclipse-product: org.eclipse.epp.package.jee.product operating system: Linux 3.5.0 (x86_64) - gtk java-runtime-version: 1.7.0_25-b15 The following plug-ins were present on the execution stack (*): 1. ch.qos.logback.classic_1.0.7.v20121108-1250 2. ch.qos.logback.core_1.0.7.v20121108-1250 3. org.eclipse.core.jobs_3.6.0.v20140424-0053 4. org.eclipse.core.runtime_3.10.0.v20140318-2214 5. org.eclipse.m2e.editor_1.5.0.20140606-0033 6. org.eclipse.m2e.logback.appender_1.5.0.20140606-0033 7. org.eclipse.osgi_3.10.0.v20140606-1445 8. org.eclipse.recommenders.stacktraces.rcp_2.1.9.v20140917-1240 Error Status: code: 0 message: Project read error fingerprint: 6f72e47b exception class: java.lang.RuntimeException exception message: Stand-In Stacktrace supplied by Eclipse Stacktraces & Error Reporting Tool number of children: 0 Topmost Stacktrace: java.lang.RuntimeException: Stand-In Stacktrace supplied by Eclipse Stacktraces & Error Reporting Tool at org.eclipse.recommenders.internal.stacktraces.rcp.LogListener.insertDebugStacktraceIfEmpty(LogListener.java:94) at org.eclipse.recommenders.internal.stacktraces.rcp.LogListener.logging(LogListener.java:76) at org.eclipse.core.internal.runtime.RuntimeLog.logToListeners(RuntimeLog.java:160) at org.eclipse.core.internal.runtime.PlatformLogWriter.logged(PlatformLogWriter.java:100) at org.eclipse.osgi.internal.log.ExtendedLogReaderServiceFactory.safeLogged(ExtendedLogReaderServiceFactory.java:86) at org.eclipse.osgi.internal.log.ExtendedLogReaderServiceFactory.logPrivileged(ExtendedLogReaderServiceFactory.java:205) at org.eclipse.osgi.internal.log.ExtendedLogReaderServiceFactory.log(ExtendedLogReaderServiceFactory.java:178) at org.eclipse.osgi.internal.log.ExtendedLogServiceFactory.log(ExtendedLogServiceFactory.java:65) at org.eclipse.osgi.internal.log.ExtendedLogServiceImpl.log(ExtendedLogServiceImpl.java:87) at org.eclipse.osgi.internal.log.LoggerImpl.log(LoggerImpl.java:54) at org.eclipse.core.internal.runtime.Log.log(Log.java:62) at org.eclipse.m2e.logback.appender.EclipseLogAppender.append(EclipseLogAppender.java:48) at org.eclipse.m2e.logback.appender.EclipseLogAppender.append(EclipseLogAppender.java:1) at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:88) at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:48) at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:280) at ch.qos.logback.classic.Logger.callAppenders(Logger.java:267) at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:449) at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:403) at ch.qos.logback.classic.Logger.error(Logger.java:566) at org.eclipse.m2e.editor.pom.DependencyTreePage$1.run(DependencyTreePage.java:253) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Messages, stacktraces, and nested status objects may be shortened. Please visit http://dev.eclipse.org/recommenders/reports/542bf9aee4b0fdd807ac4a15 for the complete error log. The list of all reported error reports belonging to this error group can be fetched from http://dev.eclipse.org/recommenders/states/542bf9afe4b0fdd807ac4a18/reports The Error Log Reporter presents the current processing state of this error to new reporters. This state can be updated by modifying the values of this bug. To update the error log database call the link below after each change made to this bug report: http://dev.eclipse.org/recommenders/states/542bf9afe4b0fdd807ac4a18/sync Thank you for caring. Your friendly error reports bot. -- * Note: The list of present bundles and their respective versions was calculated by package naming heuristics. This may or may not reflect reality.
Until m2e contributes the fixed log appender, there is not enough detail to mark this as bug or not.
*** Bug 452637 has been marked as a duplicate of this bug. ***