Clone
 

louis jacomet <louis@gradle.com> in Gradle

Make Zinc version constant public

And use it in Javadoc

Make Zinc version constant public

And use it in Javadoc

Extract Scala related version to constants

Clear error message when breaking default zinc setup

Instead of attempting to remove possible mutations to the zinc

configuration, we register an afterResolve that asserts the Scala

version required by default Zinc is valid.

Fixes #11038

Update documentation around zinc support

Add a table indicating the compatibility of Gradle / Zinc / Scala

Issue #11038

Remove unused import

Attempt at re-enabling Android smoke test

Merge branch 'release'

Compatibility fix for Gradle Module Metadata

This fix will enable Gradle 5.6.3 to consume Gradle Module Metadata for

-SNAPSHOT produced by Gradle 6+

Compatibility fix for Gradle Module Metadata

This fix will enable Gradle 5.6.3 to consume Gradle Module Metadata for

-SNAPSHOT produced by Gradle 6+

Compatibility fix for Gradle Module Metadata

This fix will enable Gradle 5.6.3 to consume Gradle Module Metadata for

-SNAPSHOT produced by Gradle 6+

Compatibility fix for Gradle Module Metadata

This fix will enable Gradle 5.6.3 to consume Gradle Module Metadata for

-SNAPSHOT produced by Gradle 6+

Fixes #11050

Add compatibility layer for SNAPSHOT metadata

Gradle 5.3 to 5.6 have an issue when publishing a Gradle Module Metadata

with a unique snapshot.

This commit enables Gradle 6+ to consume such metadata files without

error.

Fixes #9462

Add compatibility layer for SNAPSHOT metadata

Gradle 5.3 to 5.6 have an issue when publishing a Gradle Module Metadata

with a unique snapshot.

This commit enables Gradle 6+ to consume such metadata files without

error.

Add compatibility layer for SNAPSHOT metadata

Gradle 5.3 to 5.6 have an issue when publishing a Gradle Module Metadata

with a unique snapshot.

This commit enables Gradle 6+ to consume such metadata files without

error.

Do not transform UrlBackedArtifactMetadata

There is no need to start accounting for Maven specifics since the

Gradle Module Metadata properly references the exact artifact to pick.

Do not transform UrlBackedArtifactMetadata

There is no need to start accounting for Maven specifics since the

Gradle Module Metadata properly references the exact artifact to pick.

Only replace -SNAPSHOT in the URLs, not names

Only replace -SNAPSHOT in the URLs, not names

Fix unique SNAPSHOT replacement in module metadata

Previously the value was always replaced. But only the SNAPSHOT part of

a file name must be replaced, not the part in a path element.

Fix unique SNAPSHOT replacement in module metadata

Previously the value was always replaced. But only the SNAPSHOT part of

a file name must be replaced, not the part in a path element.

Fix unique SNAPSHOT replacement in module metadata

Previously the value was always replaced. But only the SNAPSHOT part of

a file name must be replaced, not the part in a path element.

Lazy illegal signing of snapshot module

Prior to this change, configuring signing in the build would always fail.

It now fails only if signing effectively happens.

Lazy illegal signing of snapshot module

Prior to this change, configuring signing in the build would always fail.

It now fails only if signing effectively happens.

No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

Update module cache content

Reference to file are now relative to the root of the module cache

instead of being absolute.

This should allow moving the full module cache around to be reused with

a different root path.

No more absolute path in metadata cache

Reference to file are now relative to the root of the module cache

instead of being absolute.

This allows moving the full module cache around to be reused with

a different root path.

The path are also normalized, so that they are portable across systems

where the name separator changes.

Issue #1338

Fix a couple Java 8 warnings

Fix a couple Java 8 warnings