Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

EPP/Obsolete/Logging

< EPP
Revision as of 05:49, 6 August 2015 by Haftsteind.gmail.com (Talk | contribs) (added debug instructions)

Mission

The logging component of EPP aims to host various utility bundles related to logging in the Eclipse IDE. At the moment, logging only contains the Automated Error Reporting utility but will likely offer a utility plugin that offers an Eclipse-wide configuration for Logback and maybe Apache Log4J in the future (hence the more general name logging instead of AERI yet).

Links

Contact

To get in touch with the committers, post your questions to the EPP forum. Preferably you prefix your post's subject with [aeri] your subject title for questions about the automated error reporting.

To start a private conversation send an email to error-reports-inbox@eclipse.org.

Update Sites

The update sites are at the moment hosted here:

No promises that these urls will be stable for all times yet.

Contributing

EPP Logging maintains an Oomph profile that provisions a complete workspace with code formatter settings etc. Simply start the Oomph installer, switch to advanced mode, select the EPP -> Logging profile and click install.

Disabling AERI in builds and runtime Eclipse

The automated error reporting disables itself if it cannot detect a system property called eclipse.buildId. This is usually the case if you execute a test suite with Maven Tycho. If you want the automated error reporting to stay enabled, set the system property to ‑Declipse.buildId=some-id in your Eclipse launch configuration.

In the case you run your test suite in a 'normal' eclipse installation which already has the buildId, you can disable error reporting completely by setting the system property ‑Dorg.eclipse.epp.logging.aeri.ui.skipReports=true.

Enable additional debug output

EPP logging can provide additional debug output to the Error Log:

  • Network exceptions if the server is unreachable (will disable the system silently by default)
  • Info output why a status or a report is filtered by the system and not propagated to the user

To enable debug tracing in your eclipse, place an .options-file with the line

org.eclipse.epp.logging.aeri.ui/debug=true

in your eclipse installation directory and start eclipse with the -debug argument.

Back to the top