Svatopluk Dedic created NETBEANS-5353:
-----------------------------------------
Summary: Do not run up-to-date compilation tasks for test runs
Key: NETBEANS-5353
URL: https://issues.apache.org/jira/browse/NETBEANS-5353
Project: NetBeans
Issue Type: Improvement
Components: projects - Gradle
Affects Versions: 12.2
Reporter: Svatopluk Dedic
Assignee: Svatopluk Dedic
Fix For: 12.4
When running {{debug.single }}project action, on a test in gradle project, the
following is executed:
{noformat}
cd /space/src/vscode/scratch/Demo22; ./gradlew --configure-on-demand
--rerun-tasks -x check test --tests com.example1.Demo22Test
{noformat}
Note the *--rerun-tasks* parameter, which will recompile classes etc, even
though gradle thinks they're up-to-date. Naturally *something* has to be done,
since otherwise Gradle won't even run the tests. As noted in
[https://www.stefan-oehme.com/stop-rerunning-tests,] Gradle should be aware of
test input changes and will decide whether to actually run the test or not.
Since this is a direct user instruction (from the IDE), we may use different
approach: run *cleanTest* task before the *test*, which will invalidate test
result from the build cache.
[~lkishalmi] – what's your opinion on the above improvement ? Is it stable /
gradle way ? It seems to work on my machine, but I lack experience with the
build system details.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
