| [cross-project-issues-dev] [aeri] Introducing server-side-managed ignore lists for Mars.1 |
| Greetings cross-projects, AERI Eclipse client got a couple of improvements - one I’d like to draw your attention to: Status filters: Status filters allow filtering of logged error statuses based on three criteria: 1. the plugin id, 2. the exception type, and 3. the status message. Status filters thus can be used to declare classes error statuses which should be ignored (like P2 errors caused by unreachable update sites or when P2 proposes alternative upgrade paths etc.) Below you find a set of filters I came up with that exclude log messages I frequently got notified about. As you see all three sections support * and $ (ends with) wildcards to match logged status objects. In case you have suggestions for further filters, please let me know. "ignoredStatuses": [ "org.eclipse.equinox.p2.*::", "org.eclipse.epp.mpc.ui:java.io.IOException:", "org.eclipse.epp.mpc.ui:java.net.SocketTimeoutException:", "org.eclipse.oomph.setup.core:$org.apache.http.ConnectionClosedException:", "org.eclipse.ui::Conflicting handlers for*", "org.eclipse.jface:java.io.IOException:Unable to resolve plug-in*", "org.eclipse.core.runtime::Invalid input url*", "org.eclipse.core.filesystem::Could not move*", "org.eclipse.core.filesystem::Could not delete*", "org.eclipse.pde.core::The current target platform contains errors*" ], Cheers, Marcel |