Versions Compared

Old Version 1

changes.mady.by.user Anna Stuchlik

Saved on

compared with

New Version 2

changes.mady.by.user Anna Stuchlik

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space ENGINES1031 and version 10.4.2

...

(error) jvmArgs = [
'--module-path', classpath.asPath,
'--add-modules', 'ALL-MODULE-PATH',
'--add-reads', "$moduleName=junit",
'--patch-module', "$moduleName=" + files(sourceSets.test.java.outputDir).asPath

]

(tick) jvmArgs += [
'--module-path', classpath.asPath,
'--add-modules', 'ALL-MODULE-PATH',
'--add-reads', "$moduleName=junit",
'--patch-module', "$moduleName=" + files(sourceSets.test.java.outputDir).asPath

]

Anchor
enable_transitive_dependencies
enable_transitive_dependencies
What if Jtest cannot resolve required dependencies while running analysis or executing tests with Maven?

To ensure that all of the required dependencies are resolved, you may need to enable resolving transitive dependencies by adding the following option to your command line:

Code Block
-Djtest.resolve.transitive=true

Why are the issue tracking tags not available in the report after I run Jtest with Maven?

Your report may not include the issue tracking tags you have configured (see Associating Tests with Development Artifacts) if Jtest is unable to resolve one or more required dependencies. To prevent this, see What if Jtest cannot resolve required dependencies while running analysis or executing tests with Maven?.

Why does test execution fail when the path to UTA files exceeds 250 characters?

...