Gretty incompatibility with Jacoco on Gradle 3.3
Gretty tasks are failing with a NPE when Jacoco-plugin is applied on Gradle 3.3.
I opened an issue at gradle: https://github.com/gradle/gradle/issues/1125
According to Stefan Wolf's response the problem is that "the Gretty plugin applies the Jacoco plugin to a DummyTask which returns null for getInputs()"
- Example project: https://github.com/jnaalisv/gradle-gretty-jacoco-issue
- Build scan URL: https://scans.gradle.com/s/j5tkhswublk4o
Same problem here :-(
I experience exactly the same problem, downgrading to gradle 3.2.1 helps for now
same problem.
@jnaalisv , @nikolauskrismer , @sander-adhese , @m4rt , the problem is fixed on "develop" branch of Gretty. I plan to do official release of Gretty 1.4.1 (with the fix) tomorrow, 1 of February, 2017.
@jnaalisv , @nikolauskrismer , @sander-adhese , @m4rt , please use Gretty 1.4.1 - jacoco should work just fine with it now.
I will try the new version as soon as it is available in the gradle plugin repo. Thanks for the new release 👍 Is there a reason why there version still 1.4.0 is listed as current (version 1.4.1 has been released three days ago)?
The fix for this issue breaks Gradle 2.x:
https://github.com/akhikhl/gretty/issues/326
Thanks, we'll test/use it soon!
I tested with the the buildfile apply from option.
For me the changes performed in version 1.4.1 fix all problems with gradle 3.3 and/or jacoco.
Thanks
I think this is related to #329 I am using the following workaround: I got the tip from http://akhikhl.github.io/gretty-doc/Code-coverage-support.html However there it says jacoco could be disabled per task which I could not figure out how.
gretty {
jacocoEnabled false
}
I experience exactly the same problem, downgrading to gradle 3.2.1 helps for now
I am using gradle 3.2.1 and facing same problem with jacoco test coverage. Any suggestion to fix it.
@jnaalisv , @nikolauskrismer , @sander-adhese , @m4rt , the problem is fixed on "develop" branch of Gretty. I plan to do official release of Gretty 1.4.1 (with the fix) tomorrow, 1 of February, 2017.
@akhikhl I am facing same issue with gradle 3.2.1 but it is working for gradle 3.0.1 please help me to fix it . I am stuck at it.