Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove unused constructor argument

  1. … 10 more files in changeset.
Remove unused constructor argument

  1. … 10 more files in changeset.
Add Java module version as a property of compile options

This is an input to the compile task and we should not read the versions

from the project state during task execution.

  1. … 17 more files in changeset.
Add Java module version as a property of compile options

This is an input to the compile task and we should not read the versions

from the project state during task execution.

  1. … 17 more files in changeset.
Replace several usages of direct `FileCollection` implementation instantiation with a factory method.

Remove a couple of `FileCollection` implementations, as these can now be replaced with public API factory methods instead.

  1. … 34 more files in changeset.
Replace several usages of direct `FileCollection` implementation instantiation with a factory method.

Remove a couple of `FileCollection` implementations, as these can now be replaced with public API factory methods instead.

  1. … 34 more files in changeset.
Replace several usages of direct `FileCollection` implementation instantiation with a factory method.

Remove a couple of `FileCollection` implementations, as these can now be replaced with public API factory methods instead.

  1. … 34 more files in changeset.
Replace several more usages of direct `FileCollection` implementation instantiation with a factory method.

Remove/deprecate a couple of `FileCollection` implementations, as these can now be replaced with public API factory methods instead.

The deprecation is intended to be tempory, until the play plugin can be updated to use public APIs instead, then the implementation will be removed.

  1. … 45 more files in changeset.
Replace several more usages of direct `FileCollection` implementation instantiation with a factory method.

Remove/deprecate a couple of `FileCollection` implementations, as these can now be replaced with public API factory methods instead.

The deprecation is intended to be tempory, until the play plugin can be updated to use public APIs instead, then the implementation will be removed.

  1. … 45 more files in changeset.
Remove CompileOptions.bootClasspath

#6297

    • -60
    • +1
    ./compile/CompileOptionsTest.groovy
  1. … 7 more files in changeset.
Add first-class support for Javac's -h option

Add the headerOutputDirectory as a compile option,

track it as an output directory and delete stale headers

when doing incremental compilation.

  1. … 20 more files in changeset.
Dogfood ImmutableFileCollection in tests (#4972)

Reduce the number of static factory methods from ImmutableFileCollection

Use layout.fileFor() in a smoke test

  1. … 31 more files in changeset.
Fix CCE when using GString compiler args

Also take into account comiler argument providers

when searching for -processorpath and -processor

arguments.

  1. … 2 more files in changeset.
Use GFileUtils.touch() only when we know the parent directory already exists

  1. … 12 more files in changeset.
Added `ObjectFactory.property(Class)` as a replacement for `ProviderFactory.property(Class)`. Changed all usages to use the new method.

  1. … 40 more files in changeset.
Introduce compiler option to store apt generated sources (#3058)

To pass on via the -s switch to javac.

  1. … 23 more files in changeset.
Make bootclasspath and bootstrapClasspath interoperate

  1. … 2 more files in changeset.
Fail when both old and new property are used in a way we cannot handle

    • -0
    • +41
    ./compile/CompileOptionsTest.groovy
  1. … 1 more file in changeset.
Replace CompileOptions.bootClasspath with FileCollection property

    • -89
    • +118
    ./compile/CompileOptionsTest.groovy
  1. … 10 more files in changeset.
Remove usage of Task.execute from tests

  1. … 29 more files in changeset.
Remove deprecated JVM platform classes and methods

- setDependencyCacheDir in java plugin and CompileOptions

- Use of Ant <depend> task and Depend options

- Javadoc setOptions

- Manifest.writeTo(Writer)

- JavaPluginConvention.setProject

Issue: #1722

    • -15
    • +0
    ./compile/CompileOptionsTest.groovy
  1. … 21 more files in changeset.
Fix JavaCompileTest

#1645

+review REVIEW-6489

Allow setting the toolchain for JavaCompile

Fixes #1645

+review REVIEW-6489

  1. … 2 more files in changeset.
Use the toolchain to track the java version for compilation

+review REVIEW-6467

  1. … 12 more files in changeset.
Fix ForkOptionsTest

+review REVIEW-6467

Track java version when using forked compilation

We introduce a new property on ForkOptions to track the Java home

which contains javac. By doing so, we are able to track the Java

version for forked compilation, too.

+review REVIEW-6467

    • -12
    • +15
    ./compile/ForkOptionsTest.groovy
  1. … 17 more files in changeset.
Take all Javadoc options into account as task inputs

Previously the type of Javadoc’s options property was MinimalJavadocOptions, which declared a few nested properties. However, the real value was a StandardJavadocDocletOptions, which contains several other properties that are not declared as inputs. Now these are taken into account as well.

This commit also stops the Javadoc task from modifying its inputs during execution.

  1. … 32 more files in changeset.
Fixes to ensure correct results when using annotation processors for Java source compilation. The fixes apply to Java compilation in both incremental and non-incremental modes.

Added `CompileOptions.annotationProcessorPath` to allow an annotation processor path to be explicitly declared for a compile task. When declared, this path is used to locate annotation processors, instead of searching the compile classpath for processors.

Added `JavaCompile.effectiveAnnotationProcessorPath` which returns the actual annotation processor path to use for compilation. This is marked with `@Classpath` so that source is recompiled when an annotation processor implementation or runtime dependency changes in some way that affects runtime execution.

The effective annotation processor path is calculated as follows:

- When explicitly set on the compile options, use this value. Can be empty.

- When an annotation processor is present in the compile classpath, use the compile classpath.

- When no annotation processors are present in the compile classspath, use an empty path.

Changed the incremental Java compile to fall back to full compile when the annotation processor path is not empty. This is an intentionally dumb strategy that can be made better later.

Made some simplifications to the generation of javac compiler args.

Added a bunch of test coverage for incremental builds in the presence of annotation processors.

  1. … 23 more files in changeset.
Revert "Flag a bunch of tests that @LeaksFileHandlers"

Now that the NativeServices initialization is fixed, these tests should

no longer leak file handles on Windows. Let's see.

This reverts commit af9d437b589adbe6688c2c7ec82eb3ba31fa5336.

  1. … 15 more files in changeset.
Flag a bunch of tests that @LeaksFileHandlers

- Now that we're correctly registering the cleanup rules, these

leaks are causing build failures on windows.

  1. … 15 more files in changeset.