| [AERI] Enbale Error Reporting for Eclipse Project with non Eclipse Prefixed plugins [message #1738826] |
Mon, 25 July 2016 09:25  |
|
I'm working on the Eclipse 4diac project. We are an incubation project and in the transition phase of migrating our code to Eclipse.org. For this we are doing a major code clean-up. It would be extremely helpful to have AERI already available during the transition phase.
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
|
|
|
| Re: [AERI] Enbale Error Reporting for Eclipse Project with non Eclipse Prefixed plugins [message #1738828 is a reply to message #1738826] |
Mon, 25 July 2016 09:55  |
|
Some questions to confirm I got your setup right. Eclipse 4diac is a stand-alone product built on top of the IDE (not just on top of the RCP)? That means you have IWorkbench, PreferencePages, EarlyStartup Hooks, and Mylyn Notifications available? If so, the integration should be straight forward: Just add org.eclipse.epp.logging.aeri.feature to your product (see the Wiki page for information like update site urls etc.).
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.
Thank you.
[1] https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/projects/5795bd6ee4b04403a3cadf19
|
|
|
| Re: [AERI] Enbale Error Reporting for Eclipse Project with non Eclipse Prefixed plugins [message #1738845 is a reply to message #1738828] |
Mon, 25 July 2016 12:20 |
|
Thanks that helped. Yes Eclipse 4diac is a stand-alone product on top of the IDE. Our application is org.eclipse.ui.ide.workbench and we should have the stuff in question available. However we are still on the E3 compatibility layer. Our product Id is "org.fordiac.ide.product"
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
|
|
|
| Re: [AERI] Enbale Error Reporting for Eclipse Project with non Eclipse Prefixed plugins [message #1738847 is a reply to message #1738845] |
Mon, 25 July 2016 12:33 |
|
There should be nothing special to do in a e3 app. Since you use Neon, I assume you are running under Java 8.
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
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03794 seconds
] 
Search
Help
Register
Login
Home
