Summary: | [api] SystemFilterPoolManager should be internal | ||
---|---|---|---|
Product: | [Tools] Target Management | Reporter: | Martin Oberhuber <mober.at+eclipse> |
Component: | RSE | Assignee: | David Dykstal <ddykstal.eclipse> |
Status: | RESOLVED FIXED | QA Contact: | Martin Oberhuber <mober.at+eclipse> |
Severity: | enhancement | ||
Priority: | P2 | Keywords: | api |
Version: | 1.0.1 | ||
Target Milestone: | 2.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Bug Depends on: | |||
Bug Blocks: | 170932 |
Description
Martin Oberhuber
2007-04-19 07:19:08 EDT
Agreed. In preparation for moving the class to org.eclipse.rse.internal.core.filters we will remove the unused static public factory method that was commented as private and change the class comments to remove all persistence policy language. I recommend that we leave the static factory method as is for now. Neither of the suggested places appear to be a good place for it. Moving the class to internal makes finding a home for this a bit less of a problem. At some point in the future the using class SubSystemConfiguration should be moved into the core plugin as well so the use of an internal class does not pose a problem at this time. [api][refactor] Move SystemFilterPoolManager to org.eclipse.rse.internal.core.filters. [target cleanup] 2.0 M7 was the original target milestone for this bug |