Community
Participate
Working Groups
WI1 (76160): Provide extension point for custom editors/viewers for opening attachments. Note: This defect covers work item 1 of enhancement #76160 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=76160) for supporting annotations for all ExecutionEvents. When the user selects the Open button for an attachment in the Log View, the attachments opens with system default editor (e.g. as determined by the SET Program class). Provide extensibility for consuming products and users to register their own actions for the Open button.
Would be possible to expose the Eclipse "Open" and "Open With" actions directly in the attachment table, I think you just need to adapt the attachement entry to IResource. You may not need a new extension point to describe this behavior as Eclipse already provides one.
See the discussion about content types in bug 135107.
This sub-feature was a new request during 4.2 and could not be contained in 4.2. Deferring to 4.3.
Sizing updated as provided by Bianaca.
Targeting to future since not containable in 4.4.
As discussed on this week's Test Project call (January 22, 2007), the Test Project will focus on existing P1 - P2/Blocker - Major and P1/Normal and test creation/automation defects (omitting defects dependant on outstanding features) in TPTP 4.4. All other Test Project defects have been targeted to future. If this defect has been targeted to future and you/originator feel it should be completed in 4.4, please provide the necessary reason as a reply to this comment or a post to the Test Project mailing list (tptp-test-tooling-dev@eclipse.org). We will collectively triage and assess our resources to determine a case-by-case decision.
Correction: The Test Project mailing list is tptp-testing-tools-dev@eclipse.org.
Changing the priority to P3 since TPTP only uses P1 - P3 priorities.
Reassigning to the Project Lead.
Currently, there are insufficient resources to contain this defect. For this defect to be considered, please re-open with an attached patch including code to resolve the symptom and test cases to test the fix.
Closing.
Correcting component.
