Revision as of 09:56, 28 March 2013

Contents

CDT Summit at EclipseCon 2013

We have scheduled a one-day CDT summit at EclipseCon 2013 in Boston, MA, on Thursday the 28th of March, 2013. To help plan for this meeting, please sign up and add any agenda items you'd like to see discussed.

Also if we don't get many more people, we can meeting in one of the evenings as well

Jeff Johnston - RedHat

Jim Adams - Analog Devices

Reibert Arbring - Ericsson

Norman Yee - Analog Devices

Leo Treggiari - Intel

Vladimir Prus - Mentor Graphics

Eric Cloninger - Klocwork

Static analysis, refactoring, Android

Mike Wrighton - Mentor Graphics

Greg Watson - IBM

Brian Watt - IBM

Teodor Madan - Freescale

Jesper Eskilson - IAR Systems

MBS, TCF, indexer

Patrick Tasse - Ericsson

Agenda

Eclipse 4.x discussion:

reactions to 4.x platform

CDT compatibility and/or upgrade plans

effect on other projects, Visualizer, etc.(e.g. if CDT retains 3.x compatibility, related plugins may need to as well)

Java 7

Advertising new CDT features

Dialog popup with "Did you know?" and "Don't show this message again"

Other?

Debug

Quick Launches (Local C/C++ App, Remote C/C++ App)

UI Junit tests: Dependency injection vs other CDT UI test techniques

Remote/synchronized projects

...

Minutes

Introductions

24 attendees from 14 companies

E4

What is the gain to start using E4 APIs?

Easier to modify the look of the UI -- No need to move CDT to E4 for that

Uniformity of the look and feel -- No need to move CDT to E4 for that

QNX feels the UI must be improved -- Does that require E4?

Once the CDT community agrees we can use E4 APIs, the decision to do so can be left to individual committers. There does not seem to be a reason we'd have to move all of CDT. We can instead take a joint E4 and 3.x approach.

Is there a reason to avoid all use of E4 APIs?

We want to keep CDT compiling on 3.x

We can re-discuss this requirement for the Luna release

Decisions

CDT 8.2 (Kepler) will not use any E4 APIs to keep compatibility with 3.x.

CDT will be free to use any new Platform APIs as long as it is not an E4 APIs. This will allow others to put CDT and the necessary part of the platform on top of 3.x.