It is a really cool Idea, as this will speed up the development, and increase the quality
IIUC your system will have, at least, these four components:
(1) a listener for each RCP Application launched from inside your development Eclipse, so you can listen to its Runtime Exceptions.
(2) human component: the RCP developer who will read the possible solutions
(3) a local running server, to which the listener will send the runtime exceptions.
(4) a remote server with the logic to suggest the cause of the RCPApp error; the possible resolution(s).
So the system can be represented by the image below:
<image.png>
My considerations below:
Human factor: The developers should insert good descriptions for cause and possible solutions > we need good documentation, maybe a sensibilization campaign.
Response: we could also find similar stacktraces over the internet, using stackoverflow or similar websites :)
Adopters: Platform UI and RCP developers are the perfect early adopters
To change your delivery options, retrieve your password, or unsubscribe from this list, visit