Róbert Papp

"If it's confusing, kill it" 😂, #22120 sounds like a good evolution. Re `NO-SOURCE` and JavaCompile, I agree in that case, but in case of `Delete` you can look at...

Sounds really familiar, is it #15406's symptom?

Oops, you're right, `gradlePluginPortal()` implies `jcenter()` in many cases: https://blog.gradle.org/jcenter-shutdown#impact-to-gradle-plugins --- but in your case this is the problem: the POM is actually different from `gradlePluginPortal()`, but that difference doesn't...

- Gradle needs to review why the metadata is different in gradlePluginPortal and elsewhere - Kotlin (YouTrack KTIJ) needs to bump the task. A bit of investigation around the issue:...

+2 I had the same issue with a different rules: just throwing my case here to maybe help the case of getting support for this in some form. I encountered...

> But an "allow operators" flag could fix this. Immediately following on from the main report, notice that it's quite easy to define non-`operator` operator function, so it's quite tricky...

Hmm, then it helps more :) Because it doesn't close your terminal when there was an error 😅, so you can read the message.

Please read the linked article, the JVM running the build and the JVM running the test are very distinct. (I just learned this myself and introduced it at work, and...

Nice compromise @3flex! JUnit 4 has `assumeTrue`/`assumeThat` which is not that declarative, but has the same result: ignores the test. I'll try to give splitting the Java versions a go...

Not necessary @Raibaz, it won't change the artifacts, only the CI. #898 (Java 8 issue) was already fixed by #900 + #907. This is just a followup to prevent it...