I didn’t explain my use-case very well.
compile with fail on warnings
fix a bunch of warnings
repeat.
The overhead of running a test just to get the file to fail to compile was
what I was avoiding. Even “assemble” was noticeably slower than
just “classes” for the mainline code.
All that said,
> I used them a _lot_ from inside IntelliJ when I was working on the
> warnings, they run faster than assemble. So I guess they were on my mind.
I don't use IntelliJ's gradle at all, actually. The gradle panel has
an option to switch to the built-in IntelliJ compiler and this works
best for me
I used them a _lot_ from inside IntelliJ when I was working on the
warnings, they run faster than assemble. So I guess they were on my mind.
testClasses in particular because, as you say, assemble doesn’t
compile the test classes (that lead to another 3,000 warnings just
when I thought I was
> - "gradlew assemble”, “gradlew dev" and “gradlew classes” do _not_ compile
> the test classes. Use “gradlew testClasses” to compile the test classes
> independently if you have a need. Executing these from within IntelliJ
> provides convenient clickable links to problems.
Hi Erick. These
