MavenPublishPomPackagingIntegTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Restore behavior of pom packaging changing the main artifact extension

This restores the behavior before #9445 (before 5.6) and with

that fixes #10555.

The behavior for non-jar packaging is still problematic and should

be changed for 6.0 as it leads to broken Gradle Module Metadata.

    • -0
    • +19
    ./MavenPublishPomPackagingIntegTest.groovy
  1. … 1 more file 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

    • -0
    • +1
    ./MavenPublishPomPackagingIntegTest.groovy
  1. … 69 more files in changeset.
Improve publishing to maven repositories with no main artifact

* GRADLE-3227 Don’t upload an additional POM file when publishing with no main artifact with ‘maven-publish’

* GRADLE-3228 Upload a POM even when no main artifact is specified with ‘maven’ plugin

    • -4
    • +2
    ./MavenPublishPomPackagingIntegTest.groovy
  1. … 2 more files in changeset.
Tweak to integration test coverage for maven-publish with packaging override

+review REVIEW-5267

    • -2
    • +5
    ./MavenPublishPomPackagingIntegTest.groovy
More integration test coverage for maven-publish with packaging override

+review REVIEW-5267

    • -0
    • +26
    ./MavenPublishPomPackagingIntegTest.groovy
Make a best effort to publish when maven publication has multiple unclassified artifacts

    • -0
    • +151
    ./MavenPublishPomPackagingIntegTest.groovy
  1. … 3 more files in changeset.