Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Recognize contributor in Zinc upgrade section

    • -0
    • +2
    /subprojects/docs/src/docs/release/notes.md
Do not clear Scala daemon environment

Remove duplicated test coverage from Scala coverage

Disallow jdk.internal imports

Fix imports for Nullable annotation

Merge remote-tracking branch 'origin/sg/60/scala-2.13.1' into release

* origin/sg/60/scala-2.13.1:

Fix unit test for DownloadingScalaToolChain

Avoid fixing Scaladoc for now

Fix unit tests

Also test Scala 2.13.0

Go back to compiling the compiler-bridge from source

Bump Scala coverage to 2.13.1

Fixes #11121

Fix unit test for DownloadingScalaToolChain

Avoid fixing Scaladoc for now

Fix unit tests

Also test Scala 2.13.0

Fix regexp for checking error message (#11167)

Fix regexp for checking error message

Fix regexp for checking error message

Test executor number can now go into two digits as well.

Fixes gradle/build-tool-flaky-tests#8

Fix formatting of angle brackets in javadoc

Fail when applying the java plugin on top of platform

Previously, this would only log a deprecation warning. With 6.0 this is

finally an error, in the same way that applying the `java-platform`

plugin on top of the `java` one is already.

Fixes #11162

Workaround for localhost lookup JDK bug (for 6.0) (#11153)

Workaround for localhost lookup JDK bug (for 6.0)

Increase timeout in integration test

Since these tests test unstable Gradle processes, they alway have

to spin up their own daemons. If the tests run in an environment short

on resources - for example if they run with several other tests in

parallel - starting up the daemon can take longer. Thus we allow

the tests to wait for up to 2 minutes now.

Increase integration test timeout

Fixes gradle/build-tool-flaky-tests#1

Increase timeout in integration test

This test runs several build in parallel and thus spins up multiple

daemons. If the test runs in an environment short on resources -

for example if it runs with several other tests in parallel - starting

up all the daemons can take longer. Thus we allow the test to wait for

up to 2 minutes now.

Fixes: https://github.com/gradle/build-tool-flaky-tests/issues/14

Increase timeout in integration test

Since this tests an unstable/broken Gradle process, it alway has

to spin up its own daemon. If the test runs in an environment short

on resources - for example if it runs with several other tests in

parallel - starting up the daemon can take longer. Thus we allow

the test to wait for up to 2 minutes now.

Fixes: https://github.com/gradle/build-tool-flaky-tests/issues/10

Use `hostname` on macOS to lookup local host name

This is to work around a five second lag when using the JDK approach, see https://bugs.openjdk.java.net/browse/JDK-8143378.

Inject hostname to OriginMetadataFactory

Fix samples

* Typo in withSourcesJar() in one sample

* Java basic sample has issues creating javadoc with the asciidoclet

under recent java -> moved the with*Jars() include to another sample.

Issue #11140

Document source and javadoc jar for feature variants

Javadoc and source jars can be configured as well for feature variants.

This is now properly documented.

Issue #11140

Register the documentation jar tasks with assemble

This makes sure the JARs are produced when using `assemble` as expected

by this task's description.

Fixes #11140

Make sure the sources jar includes resources

Previously only java sources were archived. Now all resources are

archived as well.

This matches the default of other tools.

Issue #11140

Rename methods for javadoc and sources jar creation

The new name reflects better what happens exactly when the option is

activated on the java extension.

The publication part is only applicable when a publishing plugin is also

configured.

Issue #11140

    • -2
    • +2
    /subprojects/docs/src/docs/release/notes.md
  1. … 11 more files in changeset.
Go back to compiling the compiler-bridge from source

The compiler-bridge binary jar is not guaranteed to be binary compatible

across minor versions of the Scala compiler.

This means the 2.13 bridge is not necessarily compatible with 2.13.1.

To reliably get a working compiler bridge, we need to compile from source.

Update signing sample test

Follow up to #11132

Merge pull request #11132 from gradle/ljacomet/dependency-management/docs-update

Documentation updates

Bump Scala coverage to 2.13.1