On Wed, May 11, 2016 at 9:25 AM, Nathiesha Maddage < [email protected]> wrote:
> Hi all, > > I created a git hub repository, so the project progress can easily be > tracked. > That's good , > > I could start up the plugin when the IDE starts up, > By default yes it could startup when IDE is loading however this setting should be configureable , if user need to off this service should be able to do that , you can keep that setting in eclipse preferences store Thanks and Regards /Jasintha > by implementing Istartup interface. I tested it as well. Then I created a > log listener class and attached that to the platform log, so any error is > notified. > > The next task is to filter the Dev studio plugin errors out of them. For > testing purposes, currently my code filters out the errors caused > by org.eclipse.core.runtime, and that seem to work fine. I created a very > basic dialog to notify the error, which will be triggered when an error > occurs. I will further improve the UI later. > And currently I am working on collecting the information regarding the > error, that need to be included in the report. Certain information like > plugin id, error message and severity can be easily obtained by the Istatus > object, and now I am searching for ways to fetch the other information like > java version, plugin version, osgi and bundle related information. > > GitHub Link- https://github.com/nathiesha/ErrorReportingTool.git > > > Regards > > Nathiesha > > On Thu, May 5, 2016 at 6:39 PM, Nathiesha Maddage < > [email protected]> wrote: > >> Hi all, >> >> This is the summary of the facts we discussed during the chat. >> >> >> - Original project proposal was discussed and it was confirmed that a >> new plugin would be developed for developer studio to report errors, that >> would have similar functionalities like code recommenders error reporting >> tool. >> >> >> - Certain suggestions were proposed for the original project proposal. >> >> >> 1. Instead of using an xml file to store user preferences, a separate >> preference page was suggested. >> 2. For a first time user, a dialog box to get the user input was >> suggested to be develop. The user given values for this dialog box would >> be >> stored in the preference page as well so that user can change those values >> later on using the preference page. >> 3. To get the information about the error and the error stack, the >> original idea was to read the log file and fetch the information. However >> it was suggested to make use the IStatus object instead, to get the error >> related data as it provided methods to fetch those data. >> 4. The plugin should only report the errors that is concerned with >> the developer studio. So as the first step, it was suggested to track all >> the errors caused by the developer studio plugin. This is to be >> implemented >> by listening to the error log of the dev studio plugin only. Once this >> task >> is accomplished, I was advised to implement a mechanism to filter all the >> other errors as well and find and any errors that has any connection with >> the developer studio and to report them as well. >> >> >> >> - I had an issue about registering to the error event. That you >> clarified by suggesting to do the initialization in the start method of >> the >> BundleActivator implemented plugin class. And suggested me to try changing >> the start up behavior of the plugin from the default lazy initialization >> method into some different method in the manifest file of the plugin. >> >> >> - I was asked to get started with coding, and to maintain a git-hub >> repository, so you can view and comment on the parts I have done so far. >> >> >> - I was also asked to get started with the error capturing part first >> as it is of highest priority, and then to focus on the UI and connecting >> with Jira. >> >> >> - To track the progress of the project, a milestone plan was asked to >> be prepared on daily basis. >> >> >> - It was discussed to arrange the next meeting/call in another two >> weeks time. >> >> >> >> Please point out if I have missed any important fact in our discussion. >> I am currently preparing the milestone plan. I will send it soon. >> >> Regards >> >> Nathiesha >> >> > -- *Jasintha Dasanayake* *Senior Software EngineerWSO2 Inc. | http://wso2.com <http://wso2.com/>lean . enterprise . middleware* *mobile :- 0711368118*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
