Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

  1. … 31 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

  1. … 31 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

  1. … 31 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

  1. … 31 more files in changeset.
Backport test fixture improvements from 6.0 branch

  1. … 2 more files in changeset.
Backport test fixture improvements from 6.0 branch

  1. … 2 more files in changeset.
Backport test fixture improvements from 6.0 branch

  1. … 2 more files in changeset.
Support artifacts with different names in maven module fixture

Such artifacts can actually be addressed by 'dependency artifacts'

through the 'artifact { }' notation inside a dependency declaration;

or in Gradle Module Metadata.

Support artifacts with different names in maven module fixture

Such artifacts can actually be addressed by 'dependency artifacts'

through the 'artifact { }' notation inside a dependency declaration;

or in Gradle Module Metadata.

Support artifacts with different names in maven module fixture

Such artifacts can actually be addressed by 'dependency artifacts'

through the 'artifact { }' notation inside a dependency declaration;

or in Gradle Module Metadata.

Support artifacts with different names in maven module fixture

Such artifacts can actually be addressed by 'dependency artifacts'

through the 'artifact { }' notation inside a dependency declaration;

or in Gradle Module Metadata.

Support artifacts with different names in maven module fixture

Such artifacts can actually be addressed by 'dependency artifacts'

through the 'artifact { }' notation inside a dependency declaration;

or in Gradle Module Metadata.

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. … 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

Fixes #10916

  1. … 7 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

Fixes #10916

  1. … 7 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. … 10 more files in changeset.
Fix mapping of default scope in MavenPom

* Dependencies default to compile, not runtime

* Dependency management has no default, so mapped to no_scope

Fix mapping of default scope in MavenPom

* Dependencies default to compile, not runtime

* Dependency management has no default, so mapped to no_scope

  1. … 1 more file in changeset.
Fix mapping of default scope in MavenPom

* Dependencies default to compile, not runtime

* Dependency management has no default, so mapped to no_scope

  1. … 1 more file in changeset.
Make Javadoc and sources primary variants without dependencies

  1. … 15 more files in changeset.
Make Javadoc and sources primary variants without dependencies

  1. … 15 more files in changeset.
Make Javadoc and sources primary variants without dependencies

  1. … 15 more files in changeset.
Make Javadoc and sources primary variants without dependencies

  1. … 15 more files in changeset.
Introduce multiple variations of MavenPublishJavaIntegTest

- only 'main' feature without docs

- only 'main' feature with docs

- multiple features without docs

- multiple features with docs

  1. … 5 more files in changeset.
Introduce multiple variations of MavenPublishJavaIntegTest

- only 'main' feature without docs

- only 'main' feature with docs

- multiple features without docs

- multiple features with docs

  1. … 5 more files in changeset.
Support testing with multiple features in MavenJavaModule fixture

  1. … 1 more file in changeset.
Support testing with multiple features in MavenJavaModule fixture

  1. … 1 more file in changeset.
Support testing with multiple features in MavenJavaModule fixture

  1. … 1 more file in changeset.
Prepare publishing fixtures and test to also test publication with docs

  1. … 3 more files in changeset.
Prepare publishing fixtures and test to also test publication with docs

  1. … 3 more files in changeset.