Summary: | Hyperlink detector for Java class names | ||||||
---|---|---|---|---|---|---|---|
Product: | z_Archived | Reporter: | Eugene Kuleshov <ekuleshov> | ||||
Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> | ||||
Status: | CLOSED MOVED | QA Contact: | |||||
Severity: | enhancement | ||||||
Priority: | P3 | CC: | steffen.pingel, wmitsuda | ||||
Version: | unspecified | Keywords: | bugday, helpwanted | ||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Eugene Kuleshov
2006-11-09 17:58:57 EST
*** Bug 166397 has been marked as a duplicate of this bug. *** Handling of fully-qualified class names would help with exceptions, as discussed on bug 166397: Bugzilla editor (and probably others) have nice hyperlinks to the stack trace elements, but not on the exception class. For example: java.lang.ExceptionInInitializerError at org.eclipse.mylar.internal.bugzilla.core.BugzillaAttachmentHandler.uploadAttachment(BugzillaAttachmentHandler.java:134) Mik, this is not exactly the same. Bug 166397 deal with have qualified names and "exception" or "error" keywords, like detector is already used by Console view. On the other hand, this bug is requesting hyperlinking for stuff like "BugzillaAttachmentHandler". While there is a slight difference, I want these tracked as one bug. Each bug we track adds a little overhead, and the problem and solution for these will be very closely related, which is why I inlined the exception case into this bug. I doubt that we're going to parse for "*Exception" and "*Error" because those may lead to more false positives than detecting fully qualified and camel case naming patterns. *** Bug 166397 has been marked as a duplicate of this bug. *** Some work has been completed as part of bug 239087. There is still some potential for improvement since the current hyperlink strategy requires a prefix such as "java class" or "file". Created attachment 165032 [details]
mylyn/context/zip
Steffen: Is this as easy as tuning what was contributed by the summer of code student so that we can get it into Helios? Eg, simplifying to "class BugzillaCore" and adding a setting to the Task Editor portion of the repository settings page? If so I think we should bump the priority of this so that we get to it post Helios and get some mileage on it? We would have to look into the technical details but it's not much more than a hyperlink detector to we should be able to make it work. It could even work without a prefix as long as there is some good handling of conflicts, e.g. for repositories that use CamelCase to reference wiki pages. Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |