Bug 445855 - [m2e] Error checking for warnings (err_grp: 77c7d54e)
Summary: [m2e] Error checking for warnings (err_grp: 77c7d54e)
Status: CLOSED DUPLICATE
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Recommenders (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: EPP Error Reports CLA
QA Contact:
URL:
Whiteboard: Please provide further details with a...
Keywords: needinfo
: 443977 445856 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-10-03 05:26 EDT by EPP Error Reports CLA
Modified: 2015-09-15 15:01 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description EPP Error Reports CLA 2014-10-03 05:26:24 EDT
Hello committers,

we received a new error report for Eclipse 4.5.0.I20140806-2000.


General Information:
    anonymous-id:         f8087d7b-9d38-4c73-aeb1-6991603c2a84
    eclipse-build-id:     4.5.0.I20140806-2000
    eclipse-product:      org.eclipse.epp.package.standard.product
    operating system:     MacOSX 10.9.5 (x86_64) - cocoa
    java-runtime-version: 1.8.0_20-b26

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.v20140724-1132
    5. org.eclipse.m2e.core_1.5.0.20140606-0033
    6. org.eclipse.m2e.editor.xml_1.5.0.20140606-0033
    7. org.eclipse.m2e.editor_1.5.0.20140606-0033
    8. org.eclipse.m2e.logback.appender_1.5.0.20140606-0033
    9. org.eclipse.osgi_3.10.100.v20140716-1347
    10. org.eclipse.recommenders.stacktraces.rcp_2.1.10.v20140917-1244


Error Status:
    code:                   0
    plugin:                 org.eclipse.m2e.logback.appender_1.5.0.20140606-0033
    message:                Error checking for warnings
    fingerprint:            77c7d54e
    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.xml.internal.MarkerLocationService.checkVarious(MarkerLocationService.java:573)
    at org.eclipse.m2e.editor.xml.internal.MarkerLocationService.addEditorHintMarkers(MarkerLocationService.java:241)
    at org.eclipse.m2e.core.internal.markers.MarkerUtils.addEditorHintMarkers(MarkerUtils.java:66)
    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager$4.call(ProjectRegistryManager.java:669)
    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager$4.call(ProjectRegistryManager.java:1)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.execute(ProjectRegistryManager.java:913)
    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.readMavenProjectFacade(ProjectRegistryManager.java:660)
    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:377)
    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:336)
    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob$1$1.call(ProjectRegistryRefreshJob.java:95)
    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob$1$1.call(ProjectRegistryRefreshJob.java:1)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
    at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1344)
    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob$1.call(ProjectRegistryRefreshJob.java:93)
    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob$1.call(ProjectRegistryRefreshJob.java:1)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
    at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1348)
    at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob.run(ProjectRegistryRefreshJob.java:87)
    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/542e6bc0e4b01fa99444aba9
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/542e6bc0e4b01fa99444abaa/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/542e6bc0e4b01fa99444abaa/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.
Comment 1 Marcel Bruch CLA 2014-10-04 12:57:07 EDT
*** Bug 445856 has been marked as a duplicate of this bug. ***
Comment 2 Fred Bricon CLA 2014-10-07 13:14:33 EDT
We can't analyze this report.
m2e logs it as :
catch(Exception t) {
      log.error("Error checking for warnings", t); //$NON-NLS-1$
}

but we have no information about t in this report.

We'd need step-by-step instructions / a sample project to reproduce the problem and investigate
Comment 3 Marcel Bruch CLA 2014-10-07 13:18:27 EDT
(In reply to Fred Bricon from comment #2)
> We can't analyze this report.
> m2e logs it as :
> catch(Exception t) {
>       log.error("Error checking for warnings", t); //$NON-NLS-1$
> }
> 
> but we have no information about t in this report.
> 
> We'd need step-by-step instructions / a sample project to reproduce the
> problem and investigate

Can you check whether the fixed m2e log appender will be part of SR2 and M3? then we should get more details. Will set this one to worksforme at the moment.
Comment 4 Fred Bricon CLA 2014-10-07 13:34:40 EDT
The fix in m2e log appender was committed (bug #444039), so it should be available as part of Mars M3 (If Maven 3.2.4 has been released in the mean time).
I can't tell yet if m2e 1.6 will be part of SR2, we need to discuss that decision on the ML
Comment 5 Fred Bricon CLA 2014-10-07 13:54:08 EDT
*** Bug 443977 has been marked as a duplicate of this bug. ***
Comment 6 Marcel Bruch CLA 2014-10-10 15:10:44 EDT

*** This bug has been marked as a duplicate of bug 446653 ***