Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

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

    • -2
    • +2
    ./IvyEarProjectPublishIntegrationTest.groovy
    • -6
    • +6
    ./IvyHttpPublishIntegrationTest.groovy
    • -2
    • +2
    ./IvyJavaProjectPublishIntegrationTest.groovy
    • -4
    • +4
    ./IvyLocalPublishIntegrationTest.groovy
    • -8
    • +8
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
    • -4
    • +4
    ./IvySingleProjectPublishIntegrationTest.groovy
    • -3
    • +3
    ./IvyVersionRangePublishIntegrationTest.groovy
    • -2
    • +2
    ./IvyWarProjectPublishIntegrationTest.groovy
  1. … 865 more files in changeset.
Annotate integ tests failing with instant execution in various projects

removing most of @IgnoreWithInstantExecution annotations

after fixing the @FailsWithInstantExecution rule

and more ci feedback

also make @IgnoreWithInstantExecution require a reason from a fixed set

and add it to the remaining ignores

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

    • -4
    • +3
    ./IvyHttpPublishIntegrationTest.groovy
    • -3
    • +2
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 125 more files in changeset.
Annotate integ tests failing with instant execution in various projects

after third round of CI feedback

much better, no more OOMEs, no more hung builds, no more console

replacement weirdness

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

    • -0
    • +1
    ./IvyHttpPublishIntegrationTest.groovy
  1. … 37 more files in changeset.
Annotate integ tests failing with instant execution in :ivy

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

    • -0
    • +2
    ./IvyEarProjectPublishIntegrationTest.groovy
    • -0
    • +6
    ./IvyHttpPublishIntegrationTest.groovy
    • -0
    • +2
    ./IvyJavaProjectPublishIntegrationTest.groovy
    • -0
    • +4
    ./IvyLocalPublishIntegrationTest.groovy
    • -0
    • +9
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
    • -0
    • +4
    ./IvySingleProjectPublishIntegrationTest.groovy
    • -0
    • +3
    ./IvyVersionRangePublishIntegrationTest.groovy
    • -0
    • +2
    ./IvyWarProjectPublishIntegrationTest.groovy
  1. … 20 more files in changeset.
Always apply all Category disambiguation rules

Before, parts of the platform disambiguation were only done when

using the 'java-platform' plugin. However, other consumers

may also require all rules (see #11091)

  1. … 6 more files in changeset.
Add support for sha256/sha512 to ivy publishing

Publication of SHA256 and SHA512 checksums is now enabled

on both the legacy `ivy` and `ivy-publish` plugins.

    • -0
    • +12
    ./IvyHttpPublishIntegrationTest.groovy
  1. … 9 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

    • -4
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 9 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.
Add test coverage for previously broken ivy publishing scnearios

    • -0
    • +35
    ./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.
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 tests and samples to new publishing default behavior

    • -4
    • +0
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 42 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.
Revert "Merge remote-tracking branch 'origin/sg/merges/pr-9419'"

This reverts commit 2f79026f5e127a8175e25844522237615b19ed52 because of a performance regression,

reversing changes made to 7f1e66079ce629ecde3e09e549e9796ab85761dc.

    • -1
    • +1
    ./IvyHttpPublishIntegrationTest.groovy
  1. … 90 more files in changeset.
Allow http for 127.0.0.1

Signed-off-by: Jonathan Leitschuh <Jonathan.Leitschuh@gmail.com>

    • -1
    • +1
    ./IvyHttpPublishIntegrationTest.groovy
  1. … 16 more files in changeset.
Remove utilisation of *-jars usage values

    • -12
    • +4
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 55 more files in changeset.
Allow deprecation warnings in legacy ivy plugin tests

    • -0
    • +6
    ./IvyEarProjectPublishIntegrationTest.groovy
    • -0
    • +6
    ./IvyJavaProjectPublishIntegrationTest.groovy
    • -0
    • +5
    ./IvyVersionRangePublishIntegrationTest.groovy
    • -0
    • +6
    ./IvyWarProjectPublishIntegrationTest.groovy
    • -0
    • +2
    ./SamplesIvyPublishIntegrationTest.groovy
Replace 'Matchers' with 'CoreMatchers'

So we do not require 'org.hamcrest:hamcrest-library' as additional

dependency anymore. Which was only available for most of the tests

because it leaked onto the test compile classpath.

    • -3
    • +3
    ./IvyHttpPublishIntegrationTest.groovy
  1. … 162 more files in changeset.
Publication of resolved versions for Ivy xml

While the feature was added for the Gradle metadata linked to an Ivy

publication, it was missed for the Ivy xml itself.

This commit corrects that, relying on the usage context attributes to

map the Ivy dependency to the requested resolved configuration.

Fixes #8948

    • -0
    • +23
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 11 more files in changeset.
Introduce VersionMapping support for IvyPublication

Signed-off-by: Roberto Perez Alcolea <rperezalcolea@netflix.com>

    • -0
    • +210
    ./AbstractIvyPublishIntegTest.groovy
    • -0
    • +413
    ./IvyPublishResolvedVersionsJavaIntegTest.groovy
  1. … 6 more files in changeset.
Test showing constraints published as dependencies

Using legacy ivy publication mechanism, constraints appear as

dependencies in the produced ivy.xml file.

The added test documents that fact but no changes are planned for this

legacy publication mechanism.

Issue #3667

    • -1
    • +6
    ./IvyJavaProjectPublishIntegrationTest.groovy
Use global init script to set mirrors for buildSrc (#6627)

    • -1
    • +1
    ./SamplesIvyPublishIntegrationTest.groovy
  1. … 50 more files in changeset.
Use external repository mirrors in build (#6094)

We've been bitten by external repository fluctuation for a long time.

This PR makes most of tests use repository mirrors set up by ourselves

via init script and system property.

There're still some tests not switching to mirrors, which would be fixed

in follow-up commits.

    • -2
    • +1
    ./SamplesIvyPublishIntegrationTest.groovy
  1. … 99 more files in changeset.
Apply repository mirroring to more sample tests

Also introduces a mirror for JBoss repository

    • -2
    • +9
    ./SamplesIvyPublishIntegrationTest.groovy
  1. … 32 more files in changeset.
Add test coverage for publishing configuration excludes to Ivy.xml

    • -0
    • +7
    ./IvyJavaProjectPublishIntegrationTest.groovy
  1. … 1 more file in changeset.
Use mavenCentral() and jcenter() mirrors in tests where possible

    • -3
    • +1
    ./IvyEarProjectPublishIntegrationTest.groovy
    • -3
    • +1
    ./IvyJavaProjectPublishIntegrationTest.groovy
  1. … 50 more files in changeset.
On CI redirect maven central queries to local repo for integration tests

    • -3
    • +1
    ./IvyWarProjectPublishIntegrationTest.groovy
  1. … 108 more files in changeset.