| Summary: | Change access modifier for SystemSearchPage methods to protected from private | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Tools] Target Management | Reporter: | Mohammed Ajmal <majmal> | ||||||
| Component: | RSE | Assignee: | David McKnight <dmcknigh> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | Martin Oberhuber <mober.at+eclipse> | ||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | dmcknigh, wagnross | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | 3.3 M7 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | |||||||||
| Bug Depends on: | |||||||||
| Bug Blocks: | 340072 | ||||||||
| Attachments: |
|
||||||||
|
Description
Mohammed Ajmal
Forgot to mention the version of RSE we're using: RSE 3.2.2_20110301. Created attachment 191232 [details]
patch to change some methods from private to protected
As an internal class, it would not normally be advisable to extend SystemSearchPage but it's apparently very useful in this case. We ought to consider bringing this out of the internal package at some point.
I've committed the change to cvs and opened bug 340072 for the RSE 3.2.x backport. Marking this as fixed. Marking getSearchData() as protected partially solves the problem of gaining access to user input. In addition, though, I would need the RemoteSearchData class itself to be protected as well. Then, to actually get at the data, I would need either public getters, or the fields in RemoteSearchData would need to be marked public. Created attachment 191235 [details]
additional patch to give access to RemoteSearchData inner class
I've committed the additional patch. Which plugins were affected by this bug? (In reply to comment #8) > Which plugins were affected by this bug? The affected plugin is org.eclipse.rse.files.ui. |