Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove use of deprecated API

Remove use of deprecated APIs in PluginBuilder

Replace use of archiveName with archiveFileName

Avoid more deprecated APIs

    • -6
    • +6
    ./IvySingleProjectPublishIntegrationTest.groovy
  1. … 64 more files in changeset.
Remove use of deprecated API

Remove use of deprecated APIs in PluginBuilder

Replace use of archiveName with archiveFileName

Avoid more deprecated APIs

    • -6
    • +6
    ./IvySingleProjectPublishIntegrationTest.groovy
  1. … 64 more files in changeset.
Merge branch 'feature/JLL/depricate_http_download_dependencies' of https://github.com/JLLeitschuh/gradle

* 'feature/JLL/depricate_http_download_dependencies' of https://github.com/JLLeitschuh/gradle:

Fix failing tests from insecure HTTP deprecation changes

Fix failing tests from insecure HTTP deprecation changes

Fix DefaultFlatDirArtifactRepositoryTest

Refactor HTTP deprecation logic to use HttpRedirectVerifier

Add link to medium publication about industry wide MITM

Update `@since` for new API's to be since 6.0

Disable HTTP support for TextResources in redirects by default

Fix newly added API's to use `@since 5.7`

Revert "Revert "Merge remote-tracking branch 'origin/sg/merges/pr-9419'""

    • -1
    • +1
    ./IvyHttpPublishIntegrationTest.groovy
  1. … 11 more files in changeset.
Adjust documentation to remove mention to uploadArchives

There are a number of exceptions:

- documentation of legacy plugins, in which case the docs have been

updated to say they are deprecated

- documentation of plugins related to deprecated behavior (eg, signing)

    • -42
    • +0
    ./SamplesIvyPublishIntegrationTest.groovy
  1. … 17 more files in changeset.
Adjust documentation to remove mention to uploadArchives

There are a number of exceptions:

- documentation of legacy plugins, in which case the docs have been

updated to say they are deprecated

- documentation of plugins related to deprecated behavior (eg, signing)

    • -42
    • +0
    ./SamplesIvyPublishIntegrationTest.groovy
  1. … 17 more files in changeset.
Add test coverage for previously broken ivy publishing scnearios

    • -0
    • +35
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 1 more file in changeset.
Add test coverage for previously broken ivy publishing scnearios

    • -0
    • +36
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 1 more file in changeset.
Clean up IvyPublication and publish more information to ivy.xml metadata

This cleans up the implementation of `populateFromComponent()` and

introduces the following changes that publish information which

was lossy before:

- Artifacts are now added to all configurations they belong to and

not just the first found

- Dependencies are now added for all configurations they belong to,

with the corresponding mapping and version, and

not just for the first found

- For a Java library, this means the 'runtime' now represents the full

runtime variant of the library (before, only 'default' represented

that)

    • -4
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 15 more files in changeset.
Clean up IvyPublication and publish more information to ivy.xml metadata

This cleans up the implementation of `populateFromComponent()` and

introduces the following changes that publish information which

was lossy before:

- Artifacts are now added to all configurations they belong to and

not just the first found

- Dependencies are now added for all configurations they belong to,

with the corresponding mapping and version, and

not just for the first found

- For a Java library, this means the 'runtime' now represents the full

runtime variant of the library (before, only 'default' represented

that)

    • -4
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 10 more files in changeset.
Clean up IvyPublication and publish more information to ivy.xml metadata

This cleans up the implementation of `populateFromComponent()` and

introduces the following changes that publish information which

was lossy before:

- Artifacts are now added to all configurations they belong to and

not just the first found

- Dependencies are now added for all configurations they belong to,

with the corresponding mapping and version, and

not just for the first found

- For a Java library, this means the 'runtime' now represents the full

runtime variant of the library (before, only 'default' represented

that)

    • -4
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 14 more files in changeset.
Deprecate the maven/ivy plugins

This commit introduces a deprecation warning for the `maven` plugin.

Because there's no such thing as an `ivy` plugin, we also deprecate

the _use_ of the `uploadArchives` task, which corresponds to uploading

with `ivy`, but is defined in the `base` plugin that we cannot

deprecate.

    • -0
    • +5
    ./IvyHttpPublishIntegrationTest.groovy
    • -0
    • +3
    ./IvyLocalPublishIntegrationTest.groovy
  1. … 14 more files in changeset.
Deprecate the maven/ivy plugins

This commit introduces a deprecation warning for the `maven` plugin.

Because there's no such thing as an `ivy` plugin, we also deprecate

the _use_ of the `uploadArchives` task, which corresponds to uploading

with `ivy`, but is defined in the `base` plugin that we cannot

deprecate.

    • -0
    • +5
    ./IvyHttpPublishIntegrationTest.groovy
    • -0
    • +3
    ./IvyLocalPublishIntegrationTest.groovy
  1. … 14 more files in changeset.
Adjust test fixtures and test to ivy behavior changes

    • -3
    • +3
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
    • -6
    • +6
    ./IvyVersionRangePublishIntegrationTest.groovy
  1. … 37 more files in changeset.
Fixes

    • -3
    • +3
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
    • -6
    • +6
    ./IvyVersionRangePublishIntegrationTest.groovy
  1. … 28 more files in changeset.
Fixes

    • -3
    • +3
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
    • -6
    • +6
    ./IvyVersionRangePublishIntegrationTest.groovy
  1. … 30 more files in changeset.
Adjust tests and samples to new publishing default behavior

    • -4
    • +0
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 42 more files in changeset.
Adjust tests and samples to new publishing default behavior

    • -4
    • +0
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 16 more files in changeset.
Adjust tests and samples to new publishing default behavior

    • -4
    • +0
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 16 more files in changeset.
Adjust tests and samples to new publishing default behavior

    • -4
    • +0
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 16 more files in changeset.
Remove 'experimental' variant from dependency resolution tests

With the 'GRADLE_METADATA' feature preview gone, we now only have

two dimensions of variation to test:

(1) Ivy or Maven repository?

(2) Gradle metadata available - in addition to pom or ivy - or not?

If Gradle 6+ was used for publishing, Gradle metadata is most likely

available and the pom/ivy file contains the corresponding marker.

If an older Gradle version (or Maven/Ivy) was used for publishing,

Gradle metadata is not available and there is also no marker in the

other metadata file.

  1. … 32 more files in changeset.
Remove 'experimental' variant from dependency resolution tests

With the 'GRADLE_METADATA' feature preview gone, we now only have

two dimensions of variation to test:

(1) Ivy or Maven repository?

(2) Gradle metadata available - in addition to pom or ivy - or not?

If Gradle 6+ was used for publishing, Gradle metadata is most likely

available and the pom/ivy file contains the corresponding marker.

If an older Gradle version (or Maven/Ivy) was used for publishing,

Gradle metadata is not available and there is also no marker in the

other metadata file.

  1. … 32 more files in changeset.
Remove 'experimental' variant from dependency resolution tests

With the 'GRADLE_METADATA' feature preview gone, we now only have

two dimensions of variation to test:

(1) Ivy or Maven repository?

(2) Gradle metadata available - in addition to pom or ivy - or not?

If Gradle 6+ was used for publishing, Gradle metadata is most likely

available and the pom/ivy file contains the corresponding marker.

If an older Gradle version (or Maven/Ivy) was used for publishing,

Gradle metadata is not available and there is also no marker in the

other metadata file.

  1. … 32 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

  1. … 29 more files in changeset.
Revert "Revert "Merge remote-tracking branch 'origin/sg/merges/pr-9419'""

This reverts commit 0625bc7420e55e87730673231af6ad45dd04f47a.

    • -1
    • +1
    ./IvyHttpPublishIntegrationTest.groovy
  1. … 90 more files in changeset.
Fix resolved versions of substituted dependencies

This commit fixes an inconsistency when publishing resolved

versions of a component. If that component happens to be

substituted, which would be strange for a first level dependency

but nevertheless possible, then we wouldn't find the target

module in the resolution result, and the outcome would be that

POM/IVY/Gradle Module metadata files would all have an empty

version for a substituted dependency.

With the change, we will now also look for dependencies in

the resolution result, and if one matches the original dependency

coordinates, then we use its resolved component as the result.

This allows us to _substitute_ the result with complete coordinates

in the metadata files.

Fixes nebula-plugins/gradle-nebula-integration#62

    • -0
    • +126
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 12 more files in changeset.
Fix resolved versions of substituted dependencies

This commit fixes an inconsistency when publishing resolved

versions of a component. If that component happens to be

substituted, which would be strange for a first level dependency

but nevertheless possible, then we wouldn't find the target

module in the resolution result, and the outcome would be that

POM/IVY/Gradle Module metadata files would all have an empty

version for a substituted dependency.

With the change, we will now also look for dependencies in

the resolution result, and if one matches the original dependency

coordinates, then we use its resolved component as the result.

This allows us to _substitute_ the result with complete coordinates

in the metadata files.

Fixes nebula-plugins/gradle-nebula-integration#62

    • -0
    • +126
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 12 more files in changeset.
Fix resolved versions of substituted dependencies

This commit fixes an inconsistency when publishing resolved

versions of a component. If that component happens to be

substituted, which would be strange for a first level dependency

but nevertheless possible, then we wouldn't find the target

module in the resolution result, and the outcome would be that

POM/IVY/Gradle Module metadata files would all have an empty

version for a substituted dependency.

With the change, we will now also look for dependencies in

the resolution result, and if one matches the original dependency

coordinates, then we use its resolved component as the result.

This allows us to _substitute_ the result with complete coordinates

in the metadata files.

Fixes nebula-plugins/gradle-nebula-integration#62

    • -0
    • +126
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 12 more files in changeset.
Remove outdated and unreferenced sample

    • -40
    • +0
    ./SamplesIvyPublishIntegrationTest.groovy
  1. … 7 more files in changeset.