Summary: | [api][regression] SystemNewFilterWizard.createNamePage() is no longer available | ||||||
---|---|---|---|---|---|---|---|
Product: | [Tools] Target Management | Reporter: | Samuel Wu <samuelwu> | ||||
Component: | RSE | Assignee: | David McKnight <dmcknigh> | ||||
Status: | RESOLVED FIXED | QA Contact: | Martin Oberhuber <mober.at+eclipse> | ||||
Severity: | normal | ||||||
Priority: | P1 | CC: | dmcknigh | ||||
Version: | 3.0 | Keywords: | api | ||||
Target Milestone: | 3.0 M7 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Samuel Wu
2008-04-14 11:21:55 EDT
Martin, is it possible to bring back this API as protected? We probably did this, because SystemNewFilterWizardNamePage is "internal" and having the createNamePage() method protected created an API Leak. I see, however, that the SystemNewFilterWizardInfoPage class is public API, and the corresponding createInfoPage() method is protected. I thus agree that restoring the createNamePage() method as protected makes sense, and the SystemNewFilterWizardNamePage should be made public API for consistencey. Dave can you please check whether making that class API brings in any other API leaks, and attach a patch with the modified code if it works ok. If it doesn't lead to any other problems, I'm ok with restoring that API. Please do this as early as possible such that we can get our API frozen. Created attachment 96852 [details]
patch making SystemNewFilterWizardNamePage public and createNamePage() protected
I've created a patch for this. I don't see any API leaks so I'll go ahead and commit to cvs. I've committed the changes to cvs. |