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"
< EPP
(→Documentation) |
|||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | == | + | == Sign Up == |
| − | + | ||
| + | === Eclipse.org Projects === | ||
| + | Every Eclipse project can sign up to receive error reports. To do so, file a request in [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EPP AERI's Bugzilla component]. | ||
| − | == | + | === Non-Eclipse.org Projects === |
| − | + | Non-Eclipse.org projects can signup using the free error reporting service hosted by Codetrails. Check out [https://www.codetrails.com/error-analytics/?utm_campaign=error-analytics&utm_source=eclipse-web&utm_medium=epp-wiki] for details. | |
| − | + | == Documentation == | |
| + | Check out the [https://www.codetrails.com/error-analytics/manual/?utm_campaign=error-analytics-manual&utm_source=eclipse-web&utm_medium=epp-wiki Codetrails Error Analytics manual]. | ||
| − | + | === Disabling AERI in builds and runtime Eclipse === | |
| − | + | ||
| − | + | ||
| − | = | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | == 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. | 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 | + | 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.skipReports=true'''. |
| − | Note: In Aeri | + | Note: In Aeri 1.x the property name was '''org.eclipse.epp.logging.aeri.ui.skipReports'''. |
| − | == Enable additional debug output == | + | === Enable additional debug output === |
AERI can write additional debug information to the error log, e.g.,: | AERI can write additional debug information to the error log, e.g.,: | ||
* Network exceptions on startup. | * Network exceptions on startup. | ||
| Line 64: | Line 33: | ||
== FAQ == | == FAQ == | ||
| − | === | + | === How can I collect error reports for my own Eclipse plug-ins? === |
| − | + | AERI 2.x offers an Eclipse extension point where projects can register their own servers/endpoints via plugin.xml. See [https://codetrails.com/error-analytics/manual/?utm_campaign=error-analytics-manual&utm_source=eclipse-web&utm_medium=epp-wiki] for details. | |
| − | === Can I | + | === Can I send error reports for my own Eclipse RCP applications? === |
| − | Yes | + | Yes. Watch [https://www.youtube.com/watch?v=TDSv9Tm7hGA this webinar] for details and check out the examples in the git repository. |
| − | === | + | == Contact == |
| − | + | ||
| − | + | To get in touch, post your questions to the [https://www.eclipse.org/forums/index.php/f/69/ EPP forum]. Preferably you prefix your post's subject with '''[aeri] your subject title''' for questions about the automated error reporting. | |
| − | + | ||
| − | + | If you use Mattermost, check out the [https://mattermost-test.eclipse.org/eclipse/channels/epp-aeri Mattermost EPP AERI channel]. | |
| − | + | ||
| − | |||
| − | |||
| − | + | == 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/ | ||
| − | + | URLs may change without further notice. If you need stable URLs, use the annual release train update sites. | |
| − | + | ||
| + | == 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. | ||
[[Category:EPP]] | [[Category:EPP]] | ||
Revision as of 02:37, 11 September 2017
Sign Up
Eclipse.org Projects
Every Eclipse project can sign up to receive error reports. To do so, file a request in AERI's Bugzilla component.
Non-Eclipse.org Projects
Non-Eclipse.org projects can signup using the free error reporting service hosted by Codetrails. Check out [1] for details.
Documentation
Check out the Codetrails Error Analytics manual.
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.skipReports=true.
Note: In Aeri 1.x the property name was org.eclipse.epp.logging.aeri.ui.skipReports.
Enable additional debug output
AERI can write additional debug information to the error log, e.g.,:
- Network exceptions on startup.
- Explanation why an error log event was ignored.
To enable the debug output,
- Open ${eclipse.working.dir}/.options and insert the line:
org.eclipse.epp.logging.aeri.core/debug=true
- On Mac it's .../Eclipse.app/MacOs/.options - next to the eclipse executable.
- In your eclipse.ini add the following line before the -vmargs section:
-debug
- Restart Eclipse.
Visit this page for details on how to use Platform debug tracing facility.
FAQ
How can I collect error reports for my own Eclipse plug-ins?
AERI 2.x offers an Eclipse extension point where projects can register their own servers/endpoints via plugin.xml. See [2] for details.
Can I send error reports for my own Eclipse RCP applications?
Yes. Watch this webinar for details and check out the examples in the git repository.
Contact
To get in touch, 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.
If you use Mattermost, check out the Mattermost EPP AERI channel.
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/
URLs may change without further notice. If you need stable URLs, use the annual release train update sites.
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.