I’ve noticed that there is a general sense that the majority of the users don’t
need groovy-all. How did that knowledge come about? Was there a survey that I
missed? Is there a place I can go to see the survey results? (By the way – we
depend on it in our projects).
Michael Corum
VP,
Actually in my case, @CompileStatic helped improve accuracy of coverage for
Cobertura. For Groovy/Dropwizard, I using this in my build.gradle:
Plugins {
id "net.saliman.cobertura" version "2.5.4"
}
And then later in my build.gradle, I also include:
configurations.all {
Typically, if I have something (a microservice) that is 100% covered both for
lines and branches, neither JaCoCo or Cobertura will show it properly unless I
do some things. Here are some examples of the type of things I have to do:
* Re-order methods in a class. This can make as much as
If 3.0 will still support JDK8, I’d vote for option 3 as well. If 3 will
require 9, then maybe option 2.
Michael Corum
VP, Technical Architecture Solutions
RGA Reinsurance Company
16600 Swingley Ridge Road
Chesterfield, Missouri 6301701706
T 636.736.7066
www.rgare.com
From: Paul King
problem with OpenJDK?
Is it related to Groovy or not at all?
On Sat, Sep 10, 2016 at 5:09 AM, Corum, Michael
<mco...@rgare.com<mailto:mco...@rgare.com>> wrote:
* Either one
* Alpine – I suspect others will want other options though
* Would most definitely prefer Oracle but I
* Either one
* Alpine – I suspect others will want other options though
* Would most definitely prefer Oracle but I assume other would want OpenJDK
as well. For my purposes OpenJDK just doesn’t work at all.
Michael Corum
VP, Technical Architecture Solutions
RGA Reinsurance Company
