> - "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 tasks are rather internal - classes, testClasses...
why would you need to call them explicitly? Typically you'd need to
run tests (test or check tasks) which calls (depends on) appropriate
tasks before. If you need a JAR, invoke assemble (which, correctly,
doesn't compile test classes). It's better to explain tasks that serve
high-level goals rather than low-level intermediate steps?

D.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to