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, it was a weird use case so I’ve no objection to removing those bits, I doubt many other people will have use for classes and testClasses. > On Jul 6, 2020, at 3:34 AM, Dawid Weiss <[email protected]> wrote: > >> 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 (even if they > say it's not recommended, it works just fine). > >> 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 through, siiiiggghhhh). > > When you run a test they should be compiled automatically. Does > intellij try to run > assemble for tests? That would be weird. > > > D. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
