Bug 230244 - [refactoring] Add new participant-aware refactorings to IRefactoringProcessorIds
Summary: [refactoring] Add new participant-aware refactorings to IRefactoringProcessorIds
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.7 M6   Edit
Assignee: Markus Keller CLA
QA Contact:
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2008-05-05 12:24 EDT by Markus Keller CLA
Modified: 2011-03-04 13:57 EST (History)
1 user (show)

See Also:

Attachments
Fix (8.11 KB, patch)
2011-03-04 13:56 EST, Markus Keller CLA 		no flags Details | Diff
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 Markus Keller CLA 2008-05-05 12:24:22 EDT 
I20080502-0100

Add constants for new participant-aware refactorings to IRefactoringProcessorIds and let implementations of RefactoringProcessor#getIdentifier() point to the API constants:
- ChangeSignatureProcessor
- IntroduceParameterObjectProcessor
Comment 1 Markus Keller CLA 2008-05-06 10:38:36 EDT 
Should create a new interface for the additional constants in o.e.jdt.core.manipulation (don't add to interface in jdt.ui).

These processorIds are interesting for contributors to refactoring participant extension points (e.g. org.eclipse.jdt.core.manipulation.changeMethodSignatureParticipants). The id can be used in a <with variable="..."> expression, e.g. to distinguish between changeMethodSignatureRefactoring and introduceParameterObjectRefactoring.
Comment 2 Markus Keller CLA 2011-03-04 13:56:50 EST 
Created attachment 190426 [details]
Fix
Comment 3 Markus Keller CLA 2011-03-04 13:57:36 EST 
Fixed in HEAD.