Bug 177136 - [Manifest Editor] Replace hard coded hyperlink detector with extension
Summary: [Manifest Editor] Replace hard coded hyperlink detector with extension
Status: CLOSED DUPLICATE of bug 222610
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Chris Aniszczyk CLA
QA Contact:
URL:
Whiteboard:
Keywords: bugday
Depends on:
Blocks:
 
Reported: 2007-03-13 09:34 EDT by Dani Megert CLA
Modified: 2010-11-26 14:30 EST (History)
3 users (show)

See Also:

Attachments
org.eclipse.pde.ui.patch (1.90 KB, patch)
2008-12-23 15:28 EST, Chris Aniszczyk CLA 		no flags Details | Diff
mylyn/context/zip (654 bytes, application/octet-stream)
2008-12-23 15:28 EST, Chris Aniszczyk CLA 		no flags Details
View All 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 Dani Megert CLA 2007-03-13 09:34:52 EDT 
I20070313-0800.

Since there's now extension points to contribute hyperlink detectors and hyperlink detector targets, PDE should replace their hyperlink detector from the source viewer config with an extension.
Comment 1 Chris Aniszczyk CLA 2008-12-14 22:09:00 EST 
Sounds like a plan!
Comment 2 Chris Aniszczyk CLA 2008-12-23 15:28:37 EST 
Created attachment 121179 [details]
org.eclipse.pde.ui.patch

The first step is to modify the ChangeAwareSouceViewerConfiguration to not override the behavior in JFace Text. The next step will be to add the proper extensions for hyperlink detectors and targets.
Comment 3 Chris Aniszczyk CLA 2008-12-23 15:28:40 EST 
Created attachment 121180 [details]
mylyn/context/zip
Comment 4 Chris Aniszczyk CLA 2009-05-03 18:39:14 EDT 
This will wait for 3.6, the change is too big for this stage of the game.
Comment 5 Darin Wright CLA 2010-05-12 11:33:54 EDT 
Once again, there's no reason to change this late in the game.
Comment 6 Ankur Sharma CLA 2010-11-26 14:30:32 EST 
This bug has already been fixed as part of Bug #222610

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