Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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

    • -1
    • +2
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 10 more files in changeset.
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

    • -1
    • +2
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 10 more files in changeset.
Support testing with multiple features in MavenJavaModule fixture

    • -2
    • +2
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 1 more file in changeset.
Support testing with multiple features in MavenJavaModule fixture

    • -2
    • +2
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 1 more file in changeset.
Support testing with multiple features in MavenJavaModule fixture

    • -2
    • +2
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 1 more file in changeset.
Prepare publishing fixtures and test to also test publication with docs

    • -2
    • +2
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 3 more files in changeset.
Prepare publishing fixtures and test to also test publication with docs

    • -2
    • +2
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 3 more files in changeset.
Prepare publishing fixtures and test to also test publication with docs

    • -2
    • +2
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 3 more files in changeset.
Prepare publishing fixtures and test to also test publication with docs

    • -2
    • +2
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 3 more files in changeset.
Adjust tests and samples to new publishing default behavior

    • -8
    • +1
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 43 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -8
    • +1
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -8
    • +1
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -8
    • +1
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 29 more files in changeset.
Fix for changes to PlatformSupport to service

    • -6
    • +3
    ./maven/AbstractMavenPublishIntegTest.groovy
Transition some static methods to a global service, so the implementation can be contextualized.

    • -6
    • +3
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 12 more files in changeset.
Transition some static methods to a global service, so the implementation can be contextualized.

    • -6
    • +3
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 12 more files in changeset.
Transition some static methods to a global service, so the implementation can be contextualized.

    • -6
    • +3
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 12 more files in changeset.
Update Category attribute to be typed

Adapt code to new typed attributes, dealing with coercible String values

when parsed from metadata and typed values when created inside a Gradle

build.

    • -1
    • +1
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 21 more files in changeset.
Update Category attribute to be typed

Adapt code to new typed attributes, dealing with coercible String values

when parsed from metadata and typed values when created inside a Gradle

build.

    • -1
    • +1
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 21 more files in changeset.
Update Category attribute to be typed

Adapt code to new typed attributes, dealing with coercible String values

when parsed from metadata and typed values when created inside a Gradle

build.

    • -1
    • +1
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 18 more files in changeset.
Update Category attribute to be typed

Adapt code to new typed attributes, dealing with coercible String values

when parsed from metadata and typed values when created inside a Gradle

build.

    • -1
    • +1
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 21 more files in changeset.
Update Category attribute to be typed

Adapt code to new typed attributes, dealing with coercible String values

when parsed from metadata and typed values when created inside a Gradle

build.

    • -1
    • +1
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 27 more files in changeset.
Update Category attribute to be typed

Adapt code to new typed attributes, dealing with coercible String values

when parsed from metadata and typed values when created inside a Gradle

build.

    • -1
    • +1
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 27 more files in changeset.
Rename category attribute

Attribute is now `org.gradle.category` and the constant is named

VARIANT_CATEGORY.

The removal of the "component" part of the name was to clarify to what

the category applies.

    • -1
    • +1
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 26 more files in changeset.
Rename category attribute

Attribute is now `org.gradle.category` and the constant is named

VARIANT_CATEGORY.

The removal of the "component" part of the name was to clarify to what

the category applies.

    • -1
    • +1
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 26 more files in changeset.
Rename category attribute

Attribute is now `org.gradle.category` and the constant is named

VARIANT_CATEGORY.

The removal of the "component" part of the name was to clarify to what

the category applies.

    • -1
    • +1
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 26 more files in changeset.
Support publishing optional dependencies

This commit adds support for publishing optional dependencies on Java libraries.

For now, this is really limited to Java libraries, but potentially the API can

be extended to other types of components.

If doing so, the user can attach an outgoing configuration to a Java published

component. This configuration will be considered "optional", in the sense that:

- all its dependencies will be mapped to the runtime scope of Maven components,

but using `<optional>true</optional>`

- if using Gradle metadata, additional variants will be published alongside the

main (`api` and `runtime`) variants of the library.

It is not allowed to publish an optional feature which doesn't declare at least

one capability.

    • -2
    • +8
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 19 more files in changeset.
Make sure published platforms can be consumed as enforced platforms

This commit introduces a similar strategy to what we do with

Maven metadata, but for Gradle metadata, in order to force platforms.

In fact, it uses the same code path since Gradle metadata also makes

use of Maven immutable resolve metadata. The only difference then

happens at parse time where we generate synthetic copies of platform

variants.

    • -1
    • +7
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 7 more files in changeset.
Add tests for publishing Java platforms

    • -1
    • +6
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 13 more files in changeset.
Fix failing tests after introduction of variant derivation strategy

    • -0
    • +1
    ./maven/AbstractMavenPublishIntegTest.groovy
  1. … 4 more files in changeset.