Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Replace LinkedLists with ArrayLists where possible

    • -2
    • +6
    ./compile/incremental/test/SomeClass.java
  1. … 71 more files in changeset.
Remove broken test from revert

    • -10
    • +0
    ./compile/JavaCompilerArgumentsBuilderTest.groovy
Fix merge conflict

  1. … 7 more files in changeset.
Fix merge conflict

  1. … 5 more files in changeset.
Fix merge conflict

  1. … 5 more files in changeset.
Fix merge conflict

  1. … 6 more files in changeset.
Fix merge conflict

  1. … 7 more files in changeset.
Fix merge conflict

  1. … 7 more files in changeset.
Fix merge conflict

  1. … 7 more files in changeset.
Fix merge conflict

  1. … 7 more files in changeset.
Rework how the compiler plugin is loaded

The previous implementation had a performance regression due to the inclusion of `tools.jar`

on the worker classpath. Some classes of the Java compiler were loaded multiple times. To

avoid this, we need to separate the compiler plugin from Gradle itself, so that we can load

it in isolation in the same classloader as the loader which has `tools.jar`.

Therefore, the compiler plugin is restricted to plain Java APIs, and the "communication"

with Gradle, for example the intelligence of relativizing paths or writing the generated

mapping file, is done passing lambdas to the compiler.

Last but not least, this also means that the construction of the incremental compile task

has to be done via reflection (otherwise we would load the task in the wrong classloader).

  1. … 21 more files in changeset.
Rework how the compiler plugin is loaded

The previous implementation had a performance regression due to the inclusion of `tools.jar`

on the worker classpath. Some classes of the Java compiler were loaded multiple times. To

avoid this, we need to separate the compiler plugin from Gradle itself, so that we can load

it in isolation in the same classloader as the loader which has `tools.jar`.

Therefore, the compiler plugin is restricted to plain Java APIs, and the "communication"

with Gradle, for example the intelligence of relativizing paths or writing the generated

mapping file, is done passing lambdas to the compiler.

Last but not least, this also means that the construction of the incremental compile task

has to be done via reflection (otherwise we would load the task in the wrong classloader).

  1. … 21 more files in changeset.
Rework how the compiler plugin is loaded

The previous implementation had a performance regression due to the inclusion of `tools.jar`

on the worker classpath. Some classes of the Java compiler were loaded multiple times. To

avoid this, we need to separate the compiler plugin from Gradle itself, so that we can load

it in isolation in the same classloader as the loader which has `tools.jar`.

Therefore, the compiler plugin is restricted to plain Java APIs, and the "communication"

with Gradle, for example the intelligence of relativizing paths or writing the generated

mapping file, is done passing lambdas to the compiler.

Last but not least, this also means that the construction of the incremental compile task

has to be done via reflection (otherwise we would load the task in the wrong classloader).

  1. … 21 more files in changeset.
Rework how the compiler plugin is loaded

The previous implementation had a performance regression due to the inclusion of `tools.jar`

on the worker classpath. Some classes of the Java compiler were loaded multiple times. To

avoid this, we need to separate the compiler plugin from Gradle itself, so that we can load

it in isolation in the same classloader as the loader which has `tools.jar`.

Therefore, the compiler plugin is restricted to plain Java APIs, and the "communication"

with Gradle, for example the intelligence of relativizing paths or writing the generated

mapping file, is done passing lambdas to the compiler.

Last but not least, this also means that the construction of the incremental compile task

has to be done via reflection (otherwise we would load the task in the wrong classloader).

  1. … 21 more files in changeset.
WIP

  1. … 17 more files in changeset.
WIP

  1. … 20 more files in changeset.
Rework how the compiler plugin is loaded

The previous implementation had a performance regression due to the inclusion of `tools.jar`

on the worker classpath. Some classes of the Java compiler were loaded multiple times. To

avoid this, we need to separate the compiler plugin from Gradle itself, so that we can load

it in isolation in the same classloader as the loader which has `tools.jar`.

Therefore, the compiler plugin is restricted to plain Java APIs, and the "communication"

with Gradle, for example the intelligence of relativizing paths or writing the generated

mapping file, is done passing lambdas to the compiler.

Last but not least, this also means that the construction of the incremental compile task

has to be done via reflection (otherwise we would load the task in the wrong classloader).

  1. … 21 more files in changeset.
Rework how the compiler plugin is loaded

The previous implementation had a performance regression due to the inclusion of `tools.jar`

on the worker classpath. Some classes of the Java compiler were loaded multiple times. To

avoid this, we need to separate the compiler plugin from Gradle itself, so that we can load

it in isolation in the same classloader as the loader which has `tools.jar`.

Therefore, the compiler plugin is restricted to plain Java APIs, and the "communication"

with Gradle, for example the intelligence of relativizing paths or writing the generated

mapping file, is done passing lambdas to the compiler.

Last but not least, this also means that the construction of the incremental compile task

has to be done via reflection (otherwise we would load the task in the wrong classloader).

  1. … 21 more files in changeset.
Rework how the compiler plugin is loaded

The previous implementation had a performance regression due to the inclusion of `tools.jar`

on the worker classpath. Some classes of the Java compiler were loaded multiple times. To

avoid this, we need to separate the compiler plugin from Gradle itself, so that we can load

it in isolation in the same classloader as the loader which has `tools.jar`.

Therefore, the compiler plugin is restricted to plain Java APIs, and the "communication"

with Gradle, for example the intelligence of relativizing paths or writing the generated

mapping file, is done passing lambdas to the compiler.

Last but not least, this also means that the construction of the incremental compile task

has to be done via reflection (otherwise we would load the task in the wrong classloader).

  1. … 21 more files in changeset.
Rework how the compiler plugin is loaded

The previous implementation had a performance regression due to the inclusion of `tools.jar`

on the worker classpath. Some classes of the Java compiler were loaded multiple times. To

avoid this, we need to separate the compiler plugin from Gradle itself, so that we can load

it in isolation in the same classloader as the loader which has `tools.jar`.

Therefore, the compiler plugin is restricted to plain Java APIs, and the "communication"

with Gradle, for example the intelligence of relativizing paths or writing the generated

mapping file, is done passing lambdas to the compiler.

Last but not least, this also means that the construction of the incremental compile task

has to be done via reflection (otherwise we would load the task in the wrong classloader).

  1. … 21 more files in changeset.
WIP

  1. … 20 more files in changeset.
Add property to configure the `--release` flag (#12648)

A more convenient, and provider-based, method to configure the

`--release` flag in place of using a plain compiler args like

`compilerArgs.addAll(['--release', '...'])`.

    • -0
    • +10
    ./compile/JavaCompilerArgumentsBuilderTest.groovy
  1. … 9 more files in changeset.
Add property to configure the `--release` flag

A more convenient, and provider-based, method to configure the

`--release` flag in place of using a plain compiler args like

`compilerArgs.addAll(['--release', '...'])`.

    • -0
    • +10
    ./compile/JavaCompilerArgumentsBuilderTest.groovy
  1. … 9 more files in changeset.
Add property to configure the `--release` flag

A more convenient, and provider-based, method to configure the

`--release` flag in place of using a plain compiler args like

`compilerArgs.addAll(['--release', '...'])`.

    • -0
    • +10
    ./compile/JavaCompilerArgumentsBuilderTest.groovy
  1. … 9 more files in changeset.
Add property to configure the `--release` flag

A more convenient, and provider-based, method to configure the

`--release` flag in place of using a plain compiler args like

`compilerArgs.addAll(['--release', '...'])`.

    • -0
    • +10
    ./compile/JavaCompilerArgumentsBuilderTest.groovy
  1. … 9 more files in changeset.
Add property to configure the `--release` flag

A more convenient, and provider-based, method to configure the

`--release` flag in place of using a plain compiler args like

`compilerArgs.addAll(['--release', '...'])`.

    • -0
    • +10
    ./compile/JavaCompilerArgumentsBuilderTest.groovy
  1. … 9 more files in changeset.
Add property to configure the `--release` flag

A more convenient, and provider-based, method to configure the

`--release` flag in place of using a plain compiler args like

`compilerArgs.addAll(['--release', '...'])`.

    • -0
    • +10
    ./compile/JavaCompilerArgumentsBuilderTest.groovy
  1. … 16 more files in changeset.
Add property to configure the `--release` flag

A more convenient, and provider-based, method to configure the

`--release` flag in place of using a plain compiler args like

`compilerArgs.addAll(['--release', '...'])`.

    • -0
    • +10
    ./compile/JavaCompilerArgumentsBuilderTest.groovy
  1. … 9 more files in changeset.
Add property to configure the `--release` flag

A more convenient, and provider-based, method to configure the

`--release` flag in place of using a plain compiler args like

`compilerArgs.addAll(['--release', '...'])`.

    • -0
    • +10
    ./compile/JavaCompilerArgumentsBuilderTest.groovy
  1. … 9 more files in changeset.
Allow adding 'version' and 'main class' to module-info.class

    • -10
    • +13
    ./compile/DefaultJavaCompilerFactoryTest.groovy
  1. … 6 more files in changeset.