Martin Kellogg

I'm the original reporter of #13, and I just tested this out myself and it looks fantastic. Thanks :)

Is there a time table for when this will be merged and a new release will come out? Let me know if there's anything I can do to help.

Sorry you ran into this. I'd still like to create the `checkerFrameworkAnnotatedJDK` configuration, to support older versions of the CF that use it. Here are some other ideas for possible...

> aren't we supposed to have an annotated version of the jdk? or are we now supposed to do it all ourselves The annotated JDK is no longer a separate...

This is tricky because I'm not sure how we'd detect that a different JVM is being substituted in the general case. One option would be to check whether the compile...

Definitely a gradle plugin bug. These bugs are the reason why the `skipVersionCheck` option exists. The root cause is that one of the ways we try to determine the CF...

One possible workaround for now: you can guard application of this plugin behind a Gradle property, and only supply the Gradle property when you want to run in "CI Mode"....

Hi! Sorry you are having trouble. I tried to reproduce the issue you've reported using a simple gradle repository, and I'm not seeing any problems. My attempt to reproduce is...

@blackdiz and @msridhar sorry for the delay in looking into this. `afterEvaluate` is an anti-pattern, so I decided to try to remove it entirely. The result is #219, which I...

Thanks for reporting and figuring out the root cause! I would have expected the plugin to handle your use case properly: in **some** places, we're applying CF options to all...