FYI
---------- Forwarded message ----------
From: Marcel Bruch <marcel.bruch(a)codetrails.com>
Date: Mon, Nov 23, 2015 at 3:43 AM
Subject: Re: [epp-dev] Integrate Error reporting feature with Eclipse RCP
product
To: Eclipse Packaging Project <epp-dev(a)eclipse.org>
Hi Morteza,
Aeri was built to serve the need of the Eclipse IDE. Reusing it „as-is“ in
custom products is possible but you'll likely need to specify your own Java
classes to configure Aeri for your environment. In addition there is no
external documentation available.
I assume that you are in full control of your RCP product and the
server-side where the error reports should go to. I further assume you are
familiar Eclipse development and terms like ‚features‘.
*To integrate the error reporter „as-is“ into your product*,
you need to add org.eclipse.epp.logging.aeri.feature to your product.
The latest stable version can be found on its stable update site. See [2]
for details about the available update sites.
To send error reports to your own endpoint you have to specify the *end-point
url* in your RCP client by setting a system
property „org.eclipse.epp.logging.aeri.ui.serverUrl“ [4] in your product’s
eclipse.ini.
On the server-side, you need provide a webserver that sends the „service
configuration“ under the url you configured above. See [5] for the
eclipse.org configuration. The configuration contains various settings and
urls like aboutUrl, submitUrl, problemsUrl etc. These values need to point
to your urls where you accept user requests.
*To integrate a customized error reporting into your product,*
you have to integrate org.eclipse.epp.logging.aeri.ui into your product and
specify an early startup hook that configures the system to suite your
needs. See [6] for the Eclipse IDE setup. All powers, all responsibilities,
no documentation...
I’ll stop here. There is yet no manual but I’ll add a section to the Wiki
[1] afterwards. It will evolve with your questions. Let me know where you
need more details.
Final note: Please keep in mind that Aeri has *not published any external
API*.
When using it in your product, copy the version you want to use to your
local repository.
Regards,
Marcel
[1]
https://wiki.eclipse.org/EPP/Logging
[2]
https://wiki.eclipse.org/EPP/Logging#Update_Sites
[3]
https://wiki.eclipse.org/EPP/Logging#Contributing
[4]
http://git.eclipse.org/c/epp/org.eclipse.epp.logging.git/tree/bundles/org...
[5]
https://dev.eclipse.org/recommenders/community/confess/v2/discovery
[6]
http://git.eclipse.org/c/epp/org.eclipse.epp.logging.git/tree/bundles/org...
Am 20.11.2015 um 00:56 schrieb Morteza Dehghani <mdehghan(a)usc.edu>:
Hello,
We are building an RCP-based text analysis tool at University of Southern
California called TACIT (
tacit.usc.edu), and we are eager to integrate the
new Eclipse error reporting feature in to our tool. Can you please let me
know if there is any way that we can use this feature any time soon?
Thank you,
Morteza Dehghani, PhD
Assistant Professor
Psychology, Computer Science
Brain and Creativity Institute
University of Southern California
_______________________________________________
epp-dev mailing list
epp-dev(a)eclipse.org
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev
--
Codetrails GmbH
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
_______________________________________________
epp-dev mailing list
epp-dev(a)eclipse.org
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev
--
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then
http://goo.gl/tnBgH5