MavenPublishPomCustomizationIntegTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Adjust tests and samples to new publishing default behavior

    • -2
    • +0
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 43 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
    • +0
    ./MavenPublishPomCustomizationIntegTest.groovy
  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
    • +0
    ./MavenPublishPomCustomizationIntegTest.groovy
  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
    • +0
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 32 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -1
    • +0
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -1
    • +0
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 29 more files in changeset.
Adjust tests following Gradle Module Metadata feature preview removal

    • -1
    • +0
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 29 more files in changeset.
Allow `maven-publish` with a POM that obtains group/version from parent POM

Fixes #6009

    • -1
    • +1
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 2 more files in changeset.
Allow `maven-publish` with a POM that obtains group/version from parent POM

Fixes #6009

    • -1
    • +1
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 2 more files in changeset.
Allow `maven-publish` with a POM that obtains group/version from parent POM

Fixes #6009

    • -1
    • +1
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 2 more files in changeset.
Allow `maven-publish` with a POM that obtains group/version from parent POM

Fixes #6009

    • -1
    • +1
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 2 more files in changeset.
Allow `maven-publish` with a POM that obtains group/version from parent POM

Fixes #6009

    • -1
    • +1
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 2 more files in changeset.
Allow `maven-publish` with a POM that obtains group/version from parent POM

Fixes #6009

    • -1
    • +1
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 2 more files in changeset.
Fix Gradle Module Metadata disappearing

This commit fixes an issue where using `withXml` would

erase the Gradle Module Metadata marker from generated

POM or IVY files.

This is fixed by having the marker being a finalizer,

rather than an initial step.

    • -0
    • +44
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 4 more files in changeset.
Fix Gradle Module Metadata disappearing

This commit fixes an issue where using `withXml` would

erase the Gradle Module Metadata marker from generated

POM or IVY files.

This is fixed by having the marker being a finalizer,

rather than an initial step.

    • -0
    • +44
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 4 more files in changeset.
Fix Gradle Module Metadata disappearing

This commit fixes an issue where using `withXml` would

erase the Gradle Module Metadata marker from generated

POM or IVY files.

This is fixed by having the marker being a finalizer,

rather than an initial step.

    • -0
    • +44
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 4 more files in changeset.
Add support for customizing Maven POM properties (#8341)

Add support for customizing Maven POM properties

This was previously only possible by modifying the raw POM XML tree by

calling withXml. This change adds the possibility to set Maven POM

properties using a MapProperty<String, String>.

Resolves: #5739

    • -0
    • +9
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 8 more files in changeset.
Extend POM DSL to support distributionManagement.downloadUrl

This property is used by projects to point users to alternate download locations.

Resolves #5340.

    • -0
    • +2
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 6 more files in changeset.
Use Provider API for new Maven POM DSL

Instead of postponing the migration to the Provider API by hiding getters, follow the native plugins' lead and adopt it right away.

    • -51
    • +52
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 40 more files in changeset.
Add dedicated DSL to customize POM to maven-publish plugin

This commit adds a type safe DSL for customizing the POM of a MavenPublication to the maven-publish plugin:

pom {

name 'Demo'

description 'A demonstration of Maven POM customization'

url 'http://www.example.com/project'

...

}

Only interfaces are exposed as part of the public API, all of them are prefixed with `MavenPom`.

Issue: #3348

    • -12
    • +164
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 29 more files in changeset.
Enable Gradle metadata publishing for all maven-publish tests

- Several tests are still failing

- Most of these seem related to the fact that we don't respect the modified publication coordinates

- Some required verifications are missing

- Dependency excludes are not yet supported, so we do not verify these for module metadata

    • -3
    • +2
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 19 more files in changeset.
Changed some more int tests to use junit 4.12

    • -2
    • +2
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 7 more files in changeset.
Added a little more coverge for when things go wrong generating the ivy.xml or pom.xml.

    • -0
    • +2
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 1 more file in changeset.
Initial work on new rule based configuration model, integrated into the publishing plugin.

    • -1
    • +5
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 50 more files in changeset.
use consistent spelling for `customize` throughout docs and codebase

- some minor other spelling improvements along the way

    • -0
    • +206
    ./MavenPublishPomCustomizationIntegTest.groovy
  1. … 71 more files in changeset.