Clone Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
Annotate integ tests failing with instant execution in :ivy

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

  1. … 27 more files in changeset.
Annotate integ tests failing with instant execution in :ivy

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

  1. … 27 more files in changeset.
Let ivy-publish tests not use deprecated configurations

  1. … 4 more files in changeset.
Let ivy-publish tests not use deprecated configurations

  1. … 4 more files in changeset.
Let ivy-publish tests not use deprecated configurations

  1. … 4 more files in changeset.
Let ivy-publish tests not use deprecated configurations

  1. … 4 more files in changeset.
Introduce `noComponentPublished()` expectation

This expectation needs to be used whenever we expect resolution failure because no component was published.

This happens with Gradle metadata only, as the only way to publish a module file is `from components....`

  1. … 14 more files in changeset.
Enfore looking only for `ivy` or `gradle` metadata when doing resolution

This commit uses the `metadataSources` to make sure that when we re-resolve, we only use the expected metadata source.

This prevents some tests from accidentally passing because we resolve to Ivy after failing with Gradle.

  1. … 5 more files in changeset.
Resolve published Ivy files twice, with and without Gradle metadata

This commit changes the Ivy publication tests so that we resolve the published files twice:

- once with Gradle metadata

- once without Gradle metadata

Expectations are set on both, using a single entry point (`resolveArtifacts`). This removes the

explosion of `resolveArtifact` methods.

  1. … 12 more files in changeset.
On CI redirect maven central queries to local repo for integration tests

  1. … 108 more files in changeset.
Upgrade Apache Commons Collections to v3.2.2

Version 3.2.1 has a CVSS 10.0 vulnerability. That's the worst kind of

vulnerability that exists. By merely existing on the classpath, this

library causes the Java serialization parser for the entire JVM process

to go from being a state machine to a turing machine. A turing machine

with an exec() function!




  1. … 54 more files in changeset.
Updated superclass for publish integration tests

  1. … 15 more files in changeset.
moved all s3 related resources, fixtures, tests and integration tests into resourceS3 subproject

- required to add maven/ivy testfixtures (only compiling one class each atm)

+review REVIEW-5361

  1. … 69 more files in changeset.
Changed IvyHttpModule fixture to use HttpArtifact to represent ivy and jar artifacts and removed a bunch of expect... methods from IvyHttpModule.

  1. … 29 more files in changeset.
REVIEW-1519: Create separate ivy configurations for artifacts and dependencies when publishing component - jar/war artifact is in "master" configuration - runtime deps are in "runtime" configuration - "default" extends ["master", "runtime"] - Added NamedDomainObjectContainer.maybeCreate(name)

  1. … 10 more files in changeset.
Test resolution in a bunch more ivy publish integ tests

  1. … 5 more files in changeset.
Finish off integ tests for publishing components to ivy

  1. … 6 more files in changeset.
Added 'conf' attribute to IvyArtifact, allow this to specified in ivy.xml - Don't supply conf attribute by default: will use the ivy.xml default value of '*' - Use the configuration value of a ModuleDependency to get the right hand side of the <dependency> configuration mapping. - Do a lot more ivy.xml configuration checking in integ tests.

  1. … 14 more files in changeset.
Moved setting of IvyArtifacts back off IvyConfiguration and onto IvyPublication - IvyConfiguration is a lightweight representation of a configuration element in ivy.xml - Copy runtime dependencies from Component when configured, rather than holding onto Component and doing this lazily - Added IvyDescriptorFileGenerator for translating directly from IvyPublication to ivy.xml - Translating IvyPublication -> org.apache.ivy.ModuleDescriptor -> ivy.xml meant that we couldn't produce certain ivy.xml features (like conf="*"). - Updated MavenPomFileGeneratorTest to use XmlSlurper rather than comparing actual file output. - Removed custom configurations from many integ tests - still need to add ability to set configuration on artifact/dependency - still need to add tests for configurations in ivy.xml

  1. … 17 more files in changeset.
Started rolling improvements to maven publishing over into ivy publishing (REVIEW-1268) - Prevent publishing artifact that is directory - Better error messages for publication validation failures - Many integration test improvements for ivy publication - Test for non-ascii characters in artifact names - Test for org/module/artifact/version/etc values containing whitespace

  1. … 14 more files in changeset.
Introduced IvyConfiguration to ivy-publish DSL - Added IvyConfigurationContainer and IvyConfiguration with implementations - IvyArtifacts are now added to a particular IvyConfiguration of an IvyPublication - Removed various IvyPublication.artifact* methods - Specifying a component to publish constructs the "default" and "runtime" configurations - Published artifacts are the union of artifacts from all configurations - Ivy descriptor is generated from declared configurations, rather than assuming a fixed set.

  1. … 17 more files in changeset.
Renamed/refactored ivy-publish integration tests to be more similar in structure to maven-publish integ tests

  1. … 22 more files in changeset.
Set IvyArtifact.type == extension for file-based artifacts. - Need to decide if we need to support classifier in published ivy patterns.

    • -0
    • +70
  1. … 7 more files in changeset.