[eclemma-dev] Question about CQ deadline

[Evgeny Mandrikov <mandrikov@xxxxxxxxx>]

Hi EMO IP Team,

I'm writing to you on behalf of EclEmma Team ( in copy of this email ) regarding CQ deadline (February 17/2017) as per suggestion in https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg13981.html

One of the main colors of EclEmma contribution to Oxygen release train - is to bring Eclipse code coverage plugin for Java available by default in "Eclipse IDE for Java Developers" ( https://projects.eclipse.org/projects/technology.eclemma/releases/3.0.0/plan ). We think that there is good progress towards this goal. Also AFAIK one of the main colors for Oxygen release - is Java 9 support. So will be great if EclEmma can come with Java 9 support too at a day zero, however this depends on JaCoCo coverage library (developed by us outside of Eclipse foundation).

We are closely following development of OpenJDK 9 and test JaCoCo with early access builds. We already made some changes for compatibility ( e.g. https://github.com/jacoco/jacoco/pull/434 ) and recently released JaCoCo 0.7.9 with Java 9 support that has been tested with latest JDK 9 EA b156, passed CQ for it and added it into the Eclipse Orbit. So kind of in a safe situation for now in terms of deadline, hoping that no other changes will be required on JaCoCo side anymore, but can't guarantee this till very last tests.

So could you please advise: in unlucky case when another JaCoCo release will be required, whether we can count on exception from deadline given the maturity of JaCoCo, clearness of IP, and stability of its APIs over years?

Thank you in advance.

Regards,

Evgeny Mandrikov

EclEmma Project Lead