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.
Difference between revisions of "EPP/Obsolete/Logging"
m |
m |
||
| Line 16: | Line 16: | ||
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. | 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 automated builds == | ||
| + | |||
| + | 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. | ||
| + | |||
| + | In case you want the automated error reporting to stay enabled, simply set the system property '''‑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'''. | ||
Revision as of 11:13, 9 June 2015
Links
Update Sites
The update sites are at the moment hosted here:
- http://download.eclipse.org/technology/epp/logging/stable/
- http://download.eclipse.org/technology/epp/logging/milestones/
- http://download.eclipse.org/technology/epp/logging/head/
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 automated builds
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.
In case you want the automated error reporting to stay enabled, simply set the system property ‑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.