Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Support running Gradle on JDK 10

This commit adds support for `JavaVersion.1_10` (yes, this is awkward naming, blame versioning scheme change).

Note that there are 2 different aspects of Java 10 detection:

1. given a string representation of a version number, return the appropriate `JavaVersion` enum value

2. given the current runtime, return the appropriate `JavaVersion` enum value

This commit fixes 1, but didn't change anything in the way 2 works. In particular, 2 still uses the `java.version`

property, which is then parsed and we follow the process of 1. However, since Java 9, a new `Runtime#getVersion`

method exists, that we should use instead of relying on parsing the version number returned by `java.version`.

The reason we don't do this yet is that Gradle needs to run on older JDKs, so we cannot statically link to this

method, which involves either the use of reflection or method handles to get a hand on the result of the invocation.

Since the invocation returns a complex object (not just a `String`), we're deferring this work (PRs welcome!).

Relax matching of work-in-progress items

If the items (e.g. '> IDLE') is formatted (e.g. [1B> IDLE) it is now

stripped as well. Without this, the String "> IDLE" was kept in

the output and could end up in one of the output groups.

Prepare 0.10.3 release

Bump version number {0.10.2 => 0.11.0-SNAPSHOT}

Merge pull request #2458 from gradle/rbo/release/kotlin-dsl-0.10.2

Upgrade gradle-kotlin-dsl {0.10.1 => 0.10.2}

Add note about @Inject to ObjectFactory.newInstance javadoc

Merge branch 'everyone/public-instantiator' #2393

    • -0
    • +6
    /subprojects/docs/src/docs/release/notes.md
Rename class to align with test class naming convention

Polish CodeNarc compilation classpath

    • -0
    • +1
    /subprojects/docs/src/docs/release/notes.md
Add compilationClasspath property to CodeNarc task (#2325)

Allows to configure classpath used by CodeNarc enhanced rules when compiling analyzed classes.

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.