JavaModuleExecutionIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Inject ExecOperations in JavaModuleExecutionIntegrationTest instead of using internal API

    • -4
    • +12
    ./JavaModuleExecutionIntegrationTest.groovy
Do not reference project during task execution in a test

    • -9
    • +11
    ./JavaModuleExecutionIntegrationTest.groovy
Distributed test

    • -2
    • +2
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 132 more files in changeset.
Distributed test

    • -2
    • +2
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 105 more files in changeset.
Distributed test

    • -2
    • +2
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 105 more files in changeset.
Distributed test

    • -2
    • +2
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 105 more files in changeset.
Distributed test

    • -2
    • +2
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 105 more files in changeset.
Distributed test

    • -2
    • +2
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 104 more files in changeset.
Distributed test

    • -2
    • +2
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 102 more files in changeset.
Distributed test

    • -2
    • +2
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 100 more files in changeset.
Distributed test

    • -2
    • +2
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 99 more files in changeset.
Remove Ignore

    • -2
    • +0
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 1 more file in changeset.
Distributed-test

    • -2
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 100 more files in changeset.
Distributed-test

    • -2
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 100 more files in changeset.
Distributed-test

    • -2
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 100 more files in changeset.
Distributed test

    • -2
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 101 more files in changeset.
Distributed test

    • -2
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 100 more files in changeset.
Distributed test

    • -2
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 101 more files in changeset.
Distributed test

    • -2
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 100 more files in changeset.
Distributed test

    • -2
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 104 more files in changeset.
Distributed test

    • -2
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 113 more files in changeset.
Distributed test

    • -2
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 113 more files in changeset.
Distributed test

    • -2
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 91 more files in changeset.
Distributed test

    • -2
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 92 more files in changeset.
Ignore failing instant execution tests

    • -2
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 3 more files in changeset.
Remove module version convention (#12863)

This was set to the project version by default. This breaks the cache

of a compile task even if the version is not used.

We now never set any version be default, but document how to use the

project version as the version of your Java module.

Fixes: https://github.com/gradle/gradle/issues/12860

    • -0
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 5 more files in changeset.
Remove module version convention

This was set to the project version by default. This breaks the cache

of a compile task even if the version is not used.

We now never set any version be default, but document how to use the

project version as the version of your Java module.

Fixes: https://github.com/gradle/gradle/issues/12860

    • -0
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 5 more files in changeset.
Remove module version convention

This was set to the project version by default. This breaks the cache

of a compile task even if the version is not used.

We now never set any version be default, but document how to use the

project version as the version of your Java module.

Fixes: https://github.com/gradle/gradle/issues/12860

    • -0
    • +4
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 5 more files in changeset.
Test showing how results of a separate compile step are added to module

    • -0
    • +43
    ./JavaModuleExecutionIntegrationTest.groovy
Modular app: 'run' task uses application jar instead of classes

By default, Java expects everything that belongs to one module to be

in the same location (Jar or folder). Since in Gradle resources

or outputs from different compilation steps are in separate folders,

everything that is not in the same 'classes' folder as the

module-info.class becomes unaccessible. Hence we always use the complete

Jar now to run a module via the :run task.

    • -0
    • +23
    ./JavaModuleExecutionIntegrationTest.groovy
  1. … 3 more files in changeset.