Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Try to make Scala compilation work with Zinc 1.3.0

  1. … 6 more files in changeset.
Let Gradle 6.0 work with Zinc 1.3.0

The current implementation of `org.gradle.api.internal.tasks.scala.ZincScalaCompilerFactory#getCompiler` calls `ZincUtil#getDefaultBridgeModule`,

which is an internal class, but more importantly, it's been removed in Zinc 1.3.0.

There is probably a better way to prevent the use of Zinc internal classes, but moving the functionality to determine the bridge module name

feels good enough and not too intrusive given the short time left for Gradle 6.0.

A quick try to pull in zinc 1.3.0 via the `zinc` configuration works with the patch, but fails without it.

Signed-off-by: Robert Stupp <snazy@snazy.de>

use JavaConverters and not JavaConversions in Scala code

  1. … 2 more files in changeset.
Fix checkstyle

Introduce a ScalaPluginExtension for configuring the version of Zinc used

  1. … 14 more files in changeset.
Introduce a ScalaPluginExtension for configuring the version of Zinc used

  1. … 14 more files in changeset.
Merge remote-tracking branch 'origin/wolfs/fixit/scala-plugin-zinc-update' into sg/60/zinc-upgrade-2

* origin/wolfs/fixit/scala-plugin-zinc-update:

Use forking when running in parallel

Fix IDE test expectations and mention breaking change

Document Zinc compiler upgrade

Add test case for #8421

Recognize contributor in release notes

Don't use static state

Remove unused `javaHome`

upgraded Scala zinc compiler to version 1.2.5

  1. … 21 more files in changeset.
De-incubate some more methods for Gradle 6.0

  1. … 9 more files in changeset.
Remove unnecessary implementations of CleaningJavaCompiler

  1. … 8 more files in changeset.
Merge pull request #10225 from gradle/lptr/deprecations/effective-annotation-processor-path

Remove deprecated getEffectiveAnnotationProcessorPath() method

  1. … 2 more files in changeset.
Remove AbstractCompile.compile()

The method is not useful, and incremental compiler tasks were only throwing a UnsupportedOperationException anyway.

This shouldn't break any implementing task during runtime. Compilation would break but can be fixed easily by removing the `@Override` annotation.

  1. … 4 more files in changeset.
Remove AbstractCompile.compile()

The method is not useful, and incremental compiler tasks were only throwing a UnsupportedOperationException anyway.

This shouldn't break any implementing task during runtime. Compilation would break but can be fixed easily by removing the `@Override` annotation.

  1. … 4 more files in changeset.
Use Deleter in cleaning stale outputs, take 2

This covers the remaining use cases:

- stale class cleanup for compilers

- stale overlapping output cleanup

  1. … 29 more files in changeset.
Remove GFileUtils.cleanDirectory()

  1. … 6 more files in changeset.
Remove deprecated getEffectiveAnnotationProcessorPath() method

  1. … 3 more files in changeset.
Remove deprecated getEffectiveAnnotationProcessorPath() method

  1. … 3 more files in changeset.
Remove deprecated getEffectiveAnnotationProcessorPath() method

  1. … 3 more files in changeset.
Apply `Anonymous type can be replaced with lambda` inspection the whole project

  1. … 666 more files in changeset.
Apply `Explicit type can be replaced with <>` inspection the whole project

  1. … 909 more files in changeset.
Make checkstyle happy

  1. … 3 more files in changeset.
Make checkstyle happy

  1. … 3 more files in changeset.
Make checkstyle happy

  1. … 3 more files in changeset.
Move compiler parameters into compiler implementation classes

  1. … 5 more files in changeset.
Move compiler parameters into compiler implementation classes

  1. … 5 more files in changeset.
Move compiler parameters into compiler implementation classes

  1. … 5 more files in changeset.
Move compiler parameters into compiler implementation classes

  1. … 5 more files in changeset.
Move compiler parameters into compiler implementation classes

  1. … 5 more files in changeset.
Groovy incremental compilation support (#9616)

Inspired by https://github.com/gradle/gradle/pull/9388 , this PR implements Groovy compilation avoidance. Unlike Java, things are a little more complex in Groovy compilation - a compilation unit can generate multiple classes. Thus, we introduced a `sourceClassMappingFile`, which records the source to classes mappings during the compilation process. Later, we can use this information in incremental compiler: only the affected groovy source files get recompiled in next compilation.

  1. … 73 more files in changeset.
Use isolated parameters for all worker isolation modes

  1. … 38 more files in changeset.
Use isolated parameters for all worker isolation modes

  1. … 41 more files in changeset.