Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Revert "Temporarily ignore tests"

This reverts commit 0ca3f4a19844b6173c0622f80ca22d33d77559f3.

Revert "Temporarily ignore tests"

This reverts commit 0ca3f4a19844b6173c0622f80ca22d33d77559f3.

Do not warn for explicitly declared default capabilities

Default capabilities are declared explicitly in cases were a

variant has both the default and other capabilities. The default

capability however is still recognized in resolution if only

the pom is consumed. So warning that it cannot be published to pom

is misleading.

Preserve all warnings of type 'variant unsupported'

Tighten test expectation to expose issues

Restore Kotlin DSL script deps resolver short circuit

Signed-off-by: Paul Merlin <paul@gradle.com>

Restore Kotlin DSL script deps resolver short circuit

Signed-off-by: Paul Merlin <paul@gradle.com>

Add failing test case for ObjectConfigurationAction syntax in precompiled script plugin

Remove deprecation of classes still used by the IDE script templates

Polish `KotlinSettingsScriptIntegrationTest`

Ignore specific test case instead of the whole class

Let compiled Kotlin script templates implement `PluginAware` by delegation

In order to enable `ObjectConfigurationAction` syntax (`apply {... }`)

and to preserve file resolving semantics when using a `PluginAware`

extension such as `PluginAware.apply(from: String? = null, ...)` -

init and settings scripts resolve the applied script file relative to

the applying script.

Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

In addition, this fixes the generated module metadata file which

was uploaded _without_ substution the the SNAPSHOT version with

the timestamped version when published on external repositories.

Finally, this highlighted a couple of issues with test fixtures

which were still using Gradle Module Metadata when they shouldn't.

Fixes #10916

Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

Fixes #10916

Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

Fixes #10916

Fix snapshot handling with Gradle Module Metadata

This commit fixes a couple of bugs:

1. if Gradle Module Metadata was published and consumed, then

the `changing` flag for the resolved component metadata wouldn't

be set to `true`, which means that snapshot would effectively be

considered as persistent

2. the publish test fixtures were not using the right, timestamped,

version id for the metadata and artifacts in case of unique snapshots,

which caused the resolution to fallback to the POM file

In addition, this fixes the generated module metadata file which

was uploaded _without_ substution the the SNAPSHOT version with

the timestamped version when published on external repositories.

Finally, this highlighted a couple of issues with test fixtures

which were still using Gradle Module Metadata when they shouldn't.

Fixes #10916

Merge branch 'release' into bamboo/kotlin-dsl/implicit-receivers

Make test name reflect actual behaviour

Add upgrade note

Bump to latest nightly

    • -1
    • +1
    /gradle/wrapper/gradle-wrapper.properties
Expose classes loaded by settings scripts to buildSrc

Make checkstyle happy

Make checkstyle happy

Expect plugin tasks to run before main build

Fix order of assertEquals comparison. Expected goes first

Merge remote-tracking branch 'origin/release' into ldaley/projects-inherit-settings-classpath

Use notFound() in composite build plugin resolver

Update released version to latest snapshot

Clean accepted API changes

Update version to 6.2