Eclipse Community Forums - RDF feed
https://www.eclipse.org/forums/
Eclipse Community Forums[AERI] Enbale Error Reporting for Eclipse Project with non Eclipse Prefixed plugins
https://www.eclipse.org/forums/index.php/mv/msg/1079574/1738826/#msg_1738826
I've spent quite some time on the docs and webinars but I couldn't figure out what to do and how to do it.
Is it possible to have a combined error reporting for eclipse and non eclipse prefixed plugins using the standard eclipse project error reporting infrastructure?
We have an Eclipse IDE based product.
Thanks in advance,
Alois]]>Alois Zoitl2016-07-25T09:25:04-00:00Re: [AERI] Enbale Error Reporting for Eclipse Project with non Eclipse Prefixed plugins
https://www.eclipse.org/forums/index.php/mv/msg/1079574/1738828/#msg_1738828
If it's a set of plug-ins installed into an existing Eclipse IDE installation, there is nothing to do on the client side.
On the server side, we need to adjust the filters. To do so, we need to
1. register your the project to the error reporting (your setup in [1] appears to be fine for the beginning)
2. add org.fordiac.* to the logging filters.
3. (if you have your own product) register your product name (prefix). What's your product-id?
Something that goes wrong often: Make sure that your product launch sets a system property called eclipse.buildId (newest HEAD versions also check for build.id). Otherwise AERI disables itself b/c it thinks it's running in a test workbench. See the wiki page for details.
Let me know if this already helps. If not, please share your current setup in Gerrit.
]]>Marcel Bruch2016-07-25T09:55:09-00:00Re: [AERI] Enbale Error Reporting for Eclipse Project with non Eclipse Prefixed plugins
https://www.eclipse.org/forums/index.php/mv/msg/1079574/1738845/#msg_1738845
In general I did what you suggested. The only difference is that I took the AERI feature from the Eclipse Neon update site because I couldn't get the update sites mentioned in the wiki into my target platform file. I also tested with a system.out that the eclipse.buildId is set.
However my problem is now that instead of the notification asking for sending an error I get an Eclipse Error dialog informing my about the exception. Any tips what I may have missed. Do I need to hook the AERI listener manually in E3?
Thanks,
Alois
]]>Alois Zoitl2016-07-25T12:20:54-00:00Re: [AERI] Enbale Error Reporting for Eclipse Project with non Eclipse Prefixed plugins
https://www.eclipse.org/forums/index.php/mv/msg/1079574/1738847/#msg_1738847
If you get a error dialog, this might not mean that the error was actually logged. Can you confirm that your error log view shows an error? Please post the content (press "copy to clipboard" and paste here) of that error report?
Please also check the contents of workspace folder/.metadata/.plugins/.o.e.e.logging.aeri.core. If it's emtpy aeri did not start. Please let me know what the contents of this folder is.
I also added org.fordiac.* to the list of accepted products. Before sending an error report to eclipse.org, AERI checks whether the server actually accepts the product (name), the logging bundle, and the stack trace contents.
I've updated the configuration according to your last post. See [1]. Maybe this was the last missing piece. But I can't say that for sure ATM.
[1] https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/administration/submissions]]>Marcel Bruch2016-07-25T12:33:27-00:00Re: [AERI] Enbale Error Reporting for Eclipse Project with non Eclipse Prefixed plugins
https://www.eclipse.org/forums/index.php/mv/msg/1079574/1738856/#msg_1738856
After spending more time without I think it is a dependency issue. I think just adding the org.eclipse.epp.logging.aeri.feature is not enough. For example I don't have an error log view in my setup. There is also no /.metadata/.plugins/.o.e.e.logging.aeri.core folder. Is there a list of other featueres that need to be present for aeri?
thx,
Alois]]>Alois Zoitl2016-07-25T13:33:01-00:00Re: [AERI] Enbale Error Reporting for Eclipse Project with non Eclipse Prefixed plugins
https://www.eclipse.org/forums/index.php/mv/msg/1079574/1738857/#msg_1738857
I think you should use the product or launch configuration validate buttons to see what's missing. If nothing else works, use the osgi console to run further analysis, e.g., diag org.eclipse.epp.logging.aeri.core:
WARNING: This console is connected to the current running instance of Eclipse!
osgi> diag org.eclipse.epp.logging.aeri.core
org.eclipse.epp.logging.aeri.core [229]
No resolution report for the bundle.
osgi> ss org.eclipse.epp.logging.aeri.core
"Framework is launched."
id State Bundle
229 ACTIVE org.eclipse.epp.logging.aeri.core_2.0.2.v20160630-0955
osgi>
HTH
https://git.eclipse.org/c/epp/org.eclipse.epp.logging.git/tree/features/org.eclipse.epp.logging.3rd.feature]]>Marcel Bruch2016-07-25T13:40:15-00:00Re: [AERI] Enbale Error Reporting for Eclipse Project with non Eclipse Prefixed plugins
https://www.eclipse.org/forums/index.php/mv/msg/1079574/1738873/#msg_1738873
Alois Zoitl2016-07-25T16:17:38-00:00Re: [AERI] Enbale Error Reporting for Eclipse Project with non Eclipse Prefixed plugins
https://www.eclipse.org/forums/index.php/mv/msg/1079574/1738884/#msg_1738884
Marcel Bruch2016-07-25T17:01:55-00:00Re: [AERI] Enbale Error Reporting for Eclipse Project with non Eclipse Prefixed plugins
https://www.eclipse.org/forums/index.php/mv/msg/1079574/1739214/#msg_1739214
https://blog.ctrlflow.com/setting-automated-error-reporting-eclipse-ide-based-product/