Jump to: navigation, search

Difference between revisions of "CDT/ScannerDiscovery61"

< CDT
(Links)
(The Issues)
Line 4: Line 4:
 
* Too gnu centric
 
* Too gnu centric
 
* Unable to easily refresh the discovered data when the environment changes
 
* Unable to easily refresh the discovered data when the environment changes
* The UI for setting the scanner discovery profile is very confusing
+
* The UI for setting the scanner discovery profile is very confusing. Related bugs: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=250166 250166],[https://bugs.eclipse.org/bugs/show_bug.cgi?id=255694 255694],[https://bugs.eclipse.org/bugs/show_bug.cgi?id=256374 256374],[https://bugs.eclipse.org/bugs/show_bug.cgi?id=262219 262219]
 
* Scanner Discovery data is not tied to configurations
 
* Scanner Discovery data is not tied to configurations
 
* Unable to support multiple discover providers
 
* Unable to support multiple discover providers
* Diffucult to integrate built-in discovery with Managed Build.
+
* Difficult to integrate built-in discovery with Managed Build.
 
* No consistent API for integrators to contribute Path and Macros.
 
* No consistent API for integrators to contribute Path and Macros.
  

Revision as of 11:57, 7 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. 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