Difference between revisions of "CDT/ScannerDiscovery61"

From Eclipsepedia

< CDT
Jump to: navigation, search
(New page: === 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 ...)
 
(Design and Development)
 
(19 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
=== The Issues ===
 
=== The Issues ===
  
* Difficult to create new scanner discovery profiles
+
* Difficult to create new scanner discovery profiles. Related bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=219940 219940]
* Too gnu centric
+
* Too gnu centric. Related bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=226419 226419]
* Unable to easily refresh the discovered data when the environment changes
+
* Unable to easily refresh the discovered data when the environment changes Related bugs: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=206372 206372],[https://bugs.eclipse.org/bugs/show_bug.cgi?id=142619 142619],[https://bugs.eclipse.org/bugs/show_bug.cgi?id=190902 190902],[https://bugs.eclipse.org/bugs/show_bug.cgi?id=264841 264841]
* 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 one knows the architecture of scanner discovery
 
* No one knows the architecture of scanner discovery
 +
* Build environment needs to integrate with scanner discovery.
  
 
=== The Plan ===
 
=== The Plan ===
  
1) Discover scanner discovery - document the existing architecture
+
# Discover scanner discovery - document the existing legacy architecture
2) From that figure out what we need to do
+
# Implement new scanner discovery (aka Language Settings Providers) bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=290631 290631]
 +
# Reach feature parity with old implementation
  
=== Links ===
+
=== Design and Development ===
 +
# [[CDT/ScannerDiscovery61/UseCases | What is it supposed to do anyway?]]
 +
# [[CDT/ScannerDiscovery61/ExistingArch | Existing Legacy Architecture]]
 +
# [[CDT/ScannerDiscovery61/Design | New Scanner Discovery design]]
 +
# [[CDT/ScannerDiscovery61/API | Public API for new Scanner Discovery]]
 +
# [[CDT/ScannerDiscovery61/Stories | The Stories and Alpha Version]]
  
[[CDT/ScannerDiscovery61/ExistingArch | Existing Architecture]]
+
=== Thoughts ===
 +
 
 +
* [[CDT/ScannerDiscovery61/DougThoughts | Doug's Thoughts]]
 +
* [[CDT/ScannerDiscovery61/JamesThoughts | James' Thoughts]]
 +
* [[CDT/ScannerDiscovery61/LeosThoughts | Leo's Thoughts]]
 +
* [[CDT/ScannerDiscovery61/TracyThoughts | Tracy's Thoughts]]
 +
* [[CDT/ScannerDiscovery61/LeosAddlThoughts | Leo's Additional Thoughts on Contributors]]

Latest revision as of 12:43, 13 June 2013

Contents

[edit] 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
  • Build environment needs to integrate with scanner discovery.

[edit] The Plan

  1. Discover scanner discovery - document the existing legacy architecture
  2. Implement new scanner discovery (aka Language Settings Providers) bug 290631
  3. Reach feature parity with old implementation

[edit] Design and Development

  1. What is it supposed to do anyway?
  2. Existing Legacy Architecture
  3. New Scanner Discovery design
  4. Public API for new Scanner Discovery
  5. The Stories and Alpha Version

[edit] Thoughts