Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ide-dev] Fw: Catching Exceptions via Plugin

Thank you :). BTW, fundamental discussions about the Eclipse IDE is what
this list is for.

:D

On 2013-10-18 11:26 AM, "Felix Wolff"
<felix.wolff2@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

>Though I did not want to trigger a fundamental discussion about Eclipse,
>I have to admit that I was kind of clueless as to whether this was the
>right mailing list.
>
>For starters, it would have really been good to have an architecture
>diagram of Eclipse.
>Thus I would have known where to start looking.
>I have now built a somewhat working solution: Using the IConsoloeListener
>Interface, the plugin
>reads the output of every "java" process spawned by Eclipse. I can't say
>whether this is the most elegant
>way, but it works. I receive more info than I would like, but it is now
>possible to receive the text describing an exception.
>Now I still need to find a way to react on compilations failures, because
>then no java process is spawned.
>
>I am very grateful for your kind responses and will now address my
>question to the plugin mailing list :)
>
>Thank you all!
>
>On Thu, 17 Oct 2013 17:28:19 +0200
>Mickael Istria <mistria@xxxxxxxxxx> wrote:
>
>> On 10/17/2013 04:46 PM, Doug Schaefer wrote:
>> > Mind you, I did appreciate the question. It reminds us how
>>complicated 
>> > it can be for new people to navigate our project structure and find
>> > the information they need.
>> In general, opening a bug or asking for help in a modular project is a
>> nightmare for people who don't know much of the internals of the
>> project. It makes the bar pretty high. New users don't understand much
>> about what is Platform, what is Tools, what is Technology, and probably
>> don't even understand any of the acronyms used by Eclipse projects...
>> It's not a good idea to expect such a high level of knowledge for a bug
>> report.
>> 
>> Maybe it would make sense to create an "IDE" Bugzilla component and
>>make 
>> it default component for bug reports (people using the simple bug
>>report 
>> page). People interested in IDE (we) would monitor the inbox list for
>> this entry and route it to the right component. If later someone gets
>> paid by an IDEWG to work on IDE, it would become a task of this
>>employee.
>> -- 
>> Mickael Istria
>> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
>> My blog <http://mickaelistria.wordpress.com> - My Tweets
>> <http://twitter.com/mickaelistria>
>
>
>-------
>Felix Wolff der Zweite, fürstlicher Student
>Studiengang IT-Systems Engineering
>Prof.-Dr.-Helmert-Str. 2-3 D-14482 Potsdam
>Tel.: 0331-5509-156  FAX: 0331-5509-322
>
>Design IT. Create Knowledge.
>
>Hasso-Plattner-Institut für Softwaresystemtechnik
>GmbH, Potsdam Amtsgericht Potsdam, HRB 12184
>Geschäftsführung: Prof. Dr. Christoph Meinel
>_______________________________________________
>ide-dev mailing list
>ide-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/ide-dev



Back to the top