Jump to: navigation, search

Difference between revisions of "CDT/ScannerDiscovery61"

< CDT
(The Issues)
(Links)
Line 19: Line 19:
 
=== Links ===
 
=== Links ===
  
 +
* [[CDT/ScannerDiscovery61/UseCases | What is it supposed to do anyway?]]
 
* [[CDT/ScannerDiscovery61/ExistingArch | Existing Architecture]]
 
* [[CDT/ScannerDiscovery61/ExistingArch | Existing Architecture]]
 
* [[CDT/ScannerDiscovery61/DougThoughts | Doug's Thoughts]]
 
* [[CDT/ScannerDiscovery61/DougThoughts | Doug's Thoughts]]
 
* [[CDT/ScannerDiscovery61/JamesThoughts | James' Thoughts]]
 
* [[CDT/ScannerDiscovery61/JamesThoughts | James' Thoughts]]

Revision as of 22:25, 7 September 2009

The Issues

  • Difficult to create new scanner discovery profiles. Related bug: 219940
  • Too gnu centric. Related bug: 226419
  • Unable to easily refresh the discovered data when the environment changes Related bugs: 206372,142619,190902,264841
  • The UI for setting the scanner discovery profile is very confusing. Related bugs: 250166,255694,256374,262219
  • Scanner Discovery data is not tied to configurations
  • Unable to support multiple discover providers
  • Difficult 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

  1. Discover scanner discovery - document the existing architecture
  2. From that figure out what we need to do

Links