Re: [ide-dev] A stack trace search engine to search exceptions occurring

[Patrik Suzzi <psuzzi@xxxxxxxxx>]

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: 

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

Kind Regards,

Patrik Suzzi
Software Engineer.

https://about.me/psuzzi

mobile: +39 333 39 79 300  

e-mail : psuzzi@xxxxxxxxx 

skype: patrik.suzzi

On Fri, Apr 1, 2016 at 3:40 PM, Brian de Alwis <briandealwis@xxxxxxxxx> wrote:

On 31-Mar-2016, at 5:37 AM, Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx> wrote:
> What do you think? Would something like this make sense for Eclipse - maybe just for Eclipse Runtime exceptions in the beginning?

I think it would be really valuable hooked up for debug/runtime instances as the unhandled exception handler.

Brian.

_______________________________________________
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ide-dev