Bug 152420 - provide extension point for specifying issue tracker per-plugin
Summary: provide extension point for specifying issue tracker per-plugin
Status: RESOLVED DUPLICATE of bug 150278
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: 3.0   Edit
Assignee: Mik Kersten CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-01 02:49 EDT by Mik Kersten CLA
Modified: 2007-10-03 15:53 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mik Kersten CLA 2006-08-01 02:49:39 EDT 
Now that we have the automated bug creation from the Error Log view, we could make the process easier by having each plug-in specify their bug/task/issue tracker.  Something like: 

   <extension
         point="org.eclipse.mylar.tasks.ui.repositoryBindings">
      <bugTracker
      	    plugin="org.eclipse.ajdt.ui"
            repositoryKind="bugzilla"
            repositoryUrl="https://bugs.eclipse.org/bugs"   
            autocreate="true"
            <attribute 
               name="Product" value="AJDT"
               name="Component" value="UI"/>
   </extension>
  
In orger to encourage user feedback any plug-in could specify their bug tracker association, and have it automatically created on first load.
Comment 1 Eugene Kuleshov CLA 2006-08-01 14:15:49 EDT 
How about non-plugins traces?
For instance, it could use infor from Maven's pom to do the match from stack trace to issue tracking repository.
Comment 2 Mik Kersten CLA 2006-08-01 14:45:25 EDT 
So you mean binding packages or classes to a repository?  That seems doable too, and could be surfaced by a generic exception handler that would do something like spitting out a hyperlink for submitting the bug to the right component, etc.  But create a new bug for that and specify there how you would want it to work.
Comment 3 Christophe Elek CLA 2006-08-16 13:16:16 EDT 
Regarding "But create a new bug for that and specify there how you would
want it to work.  "
can someone provide me with the new Bug number ? :)
Comment 4 Eugene Kuleshov CLA 2006-08-16 15:30:14 EDT 
(In reply to comment #3)
> Regarding "But create a new bug for that and specify there how you would
> want it to work. " can someone provide me with the new Bug number ? :)

I haven't created it.
Comment 5 Christophe Elek CLA 2006-08-16 19:51:25 EDT 
No problem :) I was just asking because we are looking at it from an Eclipse point of view :)
Not the report in itself by the idea of extension to the problem view and the message dialog framework to allow plugin provide to develop their own response to an error (send email, open web page, run tool .. or do nothing :)
Comment 6 Mik Kersten CLA 2006-08-22 18:26:55 EDT 
Christophe: in Mylar we currently have a special status handler that we delegate to everywhere.  It's role is to:
1) put an ISatuts message in the log
2) bring up a MessageDialog if requested (by a boolean "informUser" paramter)
3) trigger the automated error reporting if requested (see top of http://www.eclipse.org/mylar/doc/new.php)

It would be great if Platform provided some kind of AbstractStatusHandler mechanism, and we could register our custom bug repository aware handler instead of having a custom one.  Shall we discuss here or is there a Platform bug report for this?
Comment 7 Christophe Elek CLA 2006-08-23 08:24:10 EDT 
Mik, 
We are looking at different serviceability enhancements in Bug 154090.
A 'common handler' is part of the theme to review the message/error framework
I am pretty sure if you can give us your experience that would be great

Chris
Comment 8 Mik Kersten CLA 2006-11-20 20:35:07 EST 
We should have this for Europa, but there hasn't been demand to prioritize this for 1.0.
Comment 9 Mik Kersten CLA 2007-10-03 15:53:24 EDT 

*** This bug has been marked as a duplicate of bug 150278 ***