Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [epp-dev] Mars M5 packages

Thanks Marcel,

The exceptions I hit were definitely real problems in the code, although they were logged exceptions with no harmful consequence.  So users had been unaware.    We should be cleaning these up, but just commenting on the experience.

I'm actually very interested in leveraging these reports.   My main concern with all of these additions is a change in behavior for the many thousands of satisfied users that will encounter new dialogs and wizards we have opted in for them.  We should try to keep these to a minimum, unless they choose to participate.

Also, if a common log has been identified - is there a way to scan the server before opening up the dialog?  I realize this is an expensive network transaction, and could impact the responsiveness of the IDE.


Thanks - Chuck

Senior Architect,
WebSphere Developer Tools, Eclipse WTP PMC Lead
IBM Software Lab - Research Triangle Park, NC




From:        Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx>
To:        Eclipse Packaging Project <epp-dev@xxxxxxxxxxx>
Date:        02/06/2015 01:24 PM
Subject:        Re: [epp-dev] Mars M5 packages
Sent by:        epp-dev-bounces@xxxxxxxxxxx




Hi Chuck,

> On 06 Feb 2015, at 18:01, Chuck Bridgham <cbridgha@xxxxxxxxxx> wrote:
>
> I added my +1 vote to the Automated Error Reporting - I don't have an issue here - although it has exposed many spurious exceptions that were being thrown but ignored in the past.

I’m sorry this is not a full-hearted +1. I kindly ask for a little clarification to know how to continue with that feedback.
Are these "spurious exceptions” (i) actually problems in code, (ii) just (maybe too verbose) log messages, or is it (iii) a malfunction in the error reporter? In the latter case, it’s my duty to fix them as quickly as possible. Please let me know in this case.


> I suppose the priority to fix these will skyrocket, as the first impression is bad right now.    If the same issue has been reported...   the dialog will still occur once per user.

That is true. To some extent this is a valid goal of an error reporter added in the milestones phase. We may start talking about workarounds like [1], but if you think that these errors should not occur or should not be logged as errors, I’d prefer other solutions than that.

Please let me know what you think is (in the long run) the best solution for the platform. I’m happy to fix problems in the error reporter and help providing means to help others fixing issues in Eclipse.

FWIW, [2] is a list of feature requests we have. Please add whatever you think would make sense and vote for elements you’d like to see faster than others. We use that list to prioritize ourselves.


Marcel


[1]
https://bugs.eclipse.org/bugs/show_bug.cgi?id=442719
[2]
https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&columnlist=short_desc%2Cvotes&component=Stacktraces&f1=status_whiteboard&list_id=11052886&o1=allwordssubstr&product=Recommenders.Incubator&query_based_on=Stacktraces%20Feature%20Requests&query_format=advanced&v1=votes


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

Back to the top