MavenJavaProjectPublishIntegrationTest.groovy

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

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

    • -0
    • +5
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 39 more files in changeset.
Annotate integ tests failing with instant execution in :maven

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

    • -0
    • +5
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 39 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.

    • -0
    • +4
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 33 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.

    • -0
    • +4
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 33 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.

    • -0
    • +4
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 33 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.

    • -0
    • +4
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 33 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.

    • -0
    • +4
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 33 more files in changeset.
Allow deprecation warnings in legacy maven plugin tests

    • -0
    • +5
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 7 more files in changeset.
Allow deprecation warnings in legacy maven plugin tests

    • -0
    • +5
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 7 more files in changeset.
Allow deprecation warnings in legacy maven plugin tests

    • -0
    • +5
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 7 more files in changeset.
Allow deprecation warnings in legacy maven plugin tests

    • -0
    • +5
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 7 more files in changeset.
Allow deprecation warnings in legacy maven plugin tests

    • -0
    • +5
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 7 more files in changeset.
Allow deprecation warnings in legacy maven plugin tests

    • -0
    • +5
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 7 more files in changeset.
Allow deprecation warnings in legacy maven plugin tests

    • -0
    • +5
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 7 more files in changeset.
Allow deprecation warnings in legacy maven plugin tests

    • -0
    • +5
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 7 more files in changeset.
Use `require` instead of `prefer` in more tests

    • -1
    • +1
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 11 more files in changeset.
Fix tests after rebasing

    • -1
    • +1
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 4 more files in changeset.
Test that mutated dependencies are reflected in published metadata

Issue #3247

    • -2
    • +39
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 2 more files in changeset.
Ensure that .m2 is not polluted by integTest

    • -0
    • +2
    ./MavenJavaProjectPublishIntegrationTest.groovy
Include defaultDependencies in published metadata files for Java library

Dependencies provided via `Configuration.defaultDependencies` were omitted

from metadata files produced by the 'maven-publish' and 'ivy-publish' plugins.

This change ensures the correct dependencies are provided by `components.java`,

and these dependencies are then included in the generate pom and Ivy metadata

files.

Fixes #3238

    • -0
    • +35
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 4 more files in changeset.
Use mavenCentral() and jcenter() mirrors in tests where possible

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

    • -3
    • +1
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 108 more files in changeset.
Clean up Maven test fixture

+review REVIEW-6123

    • -4
    • +5
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 4 more files in changeset.
Maven plugin should reflect dependency exclusions for group or module in generated POM

The issue has been logged via GRADLE-3513.

+review REVIEW-6123

    • -51
    • +13
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 3 more files in changeset.
Fix for GRADLE-3440 & some improved integTests

    • -1
    • +58
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 8 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!

https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8103

https://commons.apache.org/proper/commons-collections/security-reports.html

http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/

    • -2
    • +2
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 54 more files in changeset.
Add test coverage for publishing of compile only dependencies

+review REVIEW-5807

    • -1
    • +41
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 3 more files in changeset.
make tests explicit using m2

+review REVIEW-5724

    • -0
    • +3
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 20 more files in changeset.
Revert "Override maven local repository in publish tests"

This reverts commit b78e535205444ec79f38511b07f671771cc54a38.

    • -4
    • +0
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 14 more files in changeset.
Override maven local repository in publish tests

- use directory under test directory

- maven remote publishing updates files in maven local repository.

- files are maven-metadata-remote.xml and resolver-status.properties

in each module and version

- some tests might collide when running concurrently and using a

shared maven local repository

    • -0
    • +4
    ./MavenJavaProjectPublishIntegrationTest.groovy
  1. … 14 more files in changeset.