Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Upgrade gradle-kotlin-dsl {0.10.1 => 0.10.2}

https://github.com/gradle/kotlin-dsl/releases/tag/v0.10.2

Merge pull request #418 from gradle/develop

0.10.2

Prepare 0.10.2 release

Update wrappers to latest snapshot distro

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
  1. … 10 more files in changeset.
Polish `InaccessibilityReason`

- Compute explanation on demand

- Favour data class pattern matching over method dispatch

See #416

Polish `AccessorsClassPath`

- Use lambda argument to avoid capturing parameter

Exclude tests for Java 9 builds

Fix `ConcurrentModificationException`

This commit adds guards around `holder` to make sure the list is not modified concurrently.

This fixes #2452, which was seen under heavy load.

Escape path for Windows

Don't use constants for `Usage`, make use of `ObjectFactory` instead

Except for the deprecated constructor, which needs to stick around for binary compatibility,

the default constructor of a Java library now uses a provided instance factory to create

usages.

Polish Scala annotation processing and add integration tests

    • -0
    • +1
    /subprojects/docs/src/docs/release/notes.md
Allow primitive types in extension accessors

See #416

Extract `TestWithClassPath` from `ProjectSchemaTest`

Polish `ProjectSchemaTest`

Add return type to factory functions so the correct type can be

inferred for `assertThat`.

See #416

Polish `AccessorsClassPath`

- Move members to improve top-down file readability

- Replace lambda by constructor reference

- Replace `hasFlag` by `contains` operator for reduced noise

See #416

Merge branch 'release'

Fix requires annotation (cannot be added twice)

Increase timeouts

Tests may take longer under heavy load.

Disable two Javadoc integration tests for JDK 9

There are problems with multiline javadoc header arguments in JDK 9,

and that version of javadoc, also doesn't allow using the

`@deprecated` javadoc tag, unless the thing being documented is also

annotated with the `@Deprecated` annotation. But, and here's the

kicker, if we go ahead and add `@Deprecated` the `CustomTaglet` code

spews an `IndexOutOfBounds` exception just on JDK 7 on Windows. So,

we can't make everyone happy in this same test, so, we'll just turn it

off in JDK 9 for now.

Disable two Javadoc integration tests for JDK 9

There are problems with multiline javadoc header arguments in JDK 9,

and that version of javadoc, also doesn't allow using the

`@deprecated` javadoc tag, unless the thing being documented is also

annotated with the `@Deprecated` annotation. But, and here's the

kicker, if we go ahead and add `@Deprecated` the `CustomTaglet` code

spews an `IndexOutOfBounds` exception just on JDK 7 on Windows. So,

we can't make everyone happy in this same test, so, we'll just turn it

off in JDK 9 for now.

Set annotation processor classpath in scala compile task (#2281)

Check exception message using startsWith instead of equals

Message can also be something like:

"Operation not permitted (sendto failed)"

Increase timeout

Test may take longer under heavy load.

Add Deprecated annotation

Java 9's javadoc command is more picky about having actually annotated

deprecated items if they are documented as being deprecated.

Add Deprecated annotation

Java 9's javadoc command is more picky about having actually annotated

deprecated items if they are documented as being deprecated.

Suggest to use `--scan` only once

Fix integration tests referencing old constant

Increase timeout

Test may take longer under heavy load.

Slightly increase timeout

Test may take longer under heavy load.

Store artifacts from the remote cache in the local cache

When the default local directory build cache is used, we use an optimized

way to store the downloaded artifact in the cache. Using a custom local

cache, or with the local cache disabled, a temporary file will be used

to store the downloaded artifact.

Packing is also separated from uploading to the remote cache. Again,

when the default directory cache is used to store the cached artifact in

the local cache before uploading it to the remote cache. With a custom

local cache, or when a local cache is not enabled, task outputs will be

stored in a temporary file before uploading.

Build operations are emitted separately for packing, unpacking,

uploading and downloading the cache artifact.

  1. … 42 more files in changeset.