Antony Stubbs

Took a crack at it, but can't seem to hook into the proper logging system still...

I appear to have it working via adding two different executions as per the stack over flow question: ``` org.apache.maven.plugins maven-compiler-plugin 3.8.1 org.projectlombok lombok ${lombok.version} com.github.bsideup.jabel jabel-javac-plugin 0.2.0 default-compile 8...

FYI I've moved away from this now, and am instead compiling everything on 13, targeting 8, but running fail safe multiple times on different jvms.

Ah! Thanks, I'll check it out..

@bsideup you're not referring to `java.util.logging.Logger`, are you?

Also see related: Ability to retain original groupId & artifactId #1029

@marco-brandizi I think you misunderstand me, I completely agree with you. I like the proposal in the linked issue: ``` org.jenkins-ci.plugins.workflow workflow-api 2.9-com.github:jglick:workflow-api-plugin:ea218b9-SNAPSHOT ``` I just discovered jitpack a few...

ok done, and replaced all the times I saw it in this file

Interestingly, the source validator is failing all the code snippets from the test, if they don't have a trailing `;` ``` List problems = Roaster.validateSnippet(stub); ``` ``` java.lang.IllegalArgumentException: Invalid method...

FYI here's the example - just fork uncomment it. https://github.com/google/truth/pull/894/files#diff-ac180ce002e165644a42d41860f2a235efceb7aad733ebf6751c2825cf77d996R48