Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CDT/Obsolete/ScannerDiscovery61"
(→Links) |
(→The Issues) |
||
| Line 8: | Line 8: | ||
* Unable to support multiple discover providers | * Unable to support multiple discover providers | ||
* Diffucult to integrate built-in discovery with Managed Build. | * Diffucult to integrate built-in discovery with Managed Build. | ||
| + | * No consistent API for integrators to contribute Path and Macros. | ||
* No one knows the architecture of scanner discovery | * No one knows the architecture of scanner discovery | ||
Revision as of 05:18, 5 September 2009
The Issues
- Difficult to create new scanner discovery profiles
- Too gnu centric
- Unable to easily refresh the discovered data when the environment changes
- The UI for setting the scanner discovery profile is very confusing
- Scanner Discovery data is not tied to configurations
- Unable to support multiple discover providers
- Diffucult to integrate built-in discovery with Managed Build.
- No consistent API for integrators to contribute Path and Macros.
- No one knows the architecture of scanner discovery
The Plan
- Discover scanner discovery - document the existing architecture
- From that figure out what we need to do