AbstractMavenPublishJavaIntegTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Revert "Remove sourceJar task in favor of sourcesJar (plural)"

This reverts commit a965be46

    • -2
    • +2
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 8 more files in changeset.
Remove sourceJar task in favor of sourcesJar (plural)

    • -2
    • +2
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 10 more files in changeset.
Allow a capability request without version to be published (#11691)

If a capability is required by a dependency, the request can be made

without specifying a version. This was not fully supported:

- At publishing time, we published 'version: null' (instead of nothing)

- At consuming time, we failed for a missing version (although this is fine)

Both cases are fixed in this commit and test coverage was added.

The test fixtures are extended to work with dependencies published

with a capability requests.

Fixes #11616

    • -0
    • +41
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 11 more files in changeset.
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

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

    • -23
    • +23
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 872 more files in changeset.
Annotate integ tests failing with instant execution in :maven

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

    • -0
    • +23
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 39 more files in changeset.
Rename methods for javadoc and sources jar creation

The new name reflects better what happens exactly when the option is

activated on the java extension.

The publication part is only applicable when a publishing plugin is also

configured.

Issue #11140

    • -2
    • +2
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 25 more files in changeset.
Rename methods for javadoc and sources jar creation

The new name reflects better what happens exactly when the option is

activated on the java extension.

The publication part is only applicable when a publishing plugin is also

configured.

Issue #11140

    • -2
    • +2
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 24 more files in changeset.
Fix publication warning report

An output is no longer presented if all warnings are silenced by variant

name.

Fixes #11111

    • -15
    • +15
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 3 more files in changeset.
Do not warn for explicitly declared default capabilities

Default capabilities are declared explicitly in cases were a

variant has both the default and other capabilities. The default

capability however is still recognized in resolution if only

the pom is consumed. So warning that it cannot be published to pom

is misleading.

    • -0
    • +44
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 1 more file in changeset.
Tighten test expectation to expose issues

    • -2
    • +15
    ./AbstractMavenPublishJavaIntegTest.groovy
Merge remote-tracking branch 'origin/sg/60/baseplugin-deprecate' into release

* origin/sg/60/baseplugin-deprecate:

Fix santatracker performance template reference to buildClassPath

Fix smoke test with expected deprecation message

Fix Play unit test

Update samples to avoid deprecated APIs

Avoid more deprecated APIs

Avoid

Re-enable disabled test

Do not nag on deprecated archive task properties until Kotlin plugin is updated

Remove gretty plugin from sample

Support Providers in manifest attributes

Make BuildClassPath more idiomatic

Remove use of deprecated API

Update application plugin to use lambdas and use new Provider API methods

Restore old behavior of distribution plugin validation

Use Provider API in Distribution plugin too

Use lambdas and avoid use of deprecated archive APIs

Add nags for deprecated AbstractArchiveTask methods

Add replacements for BasePlugin.libsDir BasePlugin.distsDir

    • -1
    • +1
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 1 more file in changeset.
Do not define scope for dependencyManagement entries

The semantics between the configuration of a constraint in Gradle and the scope

of a declaration in dependencyManagement in Maven are fundamentally

different.

Given this, Gradle will no longer attempt to define a scope for

dependencyManagement entries when creating POM files.

The only exception is the import scope as it carries special meaning.

Fixes #10878

    • -5
    • +4
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 4 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

    • -1
    • +1
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 64 more files in changeset.
Make Javadoc and sources primary variants without dependencies

    • -1
    • +4
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 15 more files in changeset.
Configure Javadoc and sources separately and create tasks only on demand

    • -2
    • +2
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 34 more files in changeset.
Introduce multiple variations of MavenPublishJavaIntegTest

- only 'main' feature without docs

- only 'main' feature with docs

- multiple features without docs

- multiple features with docs

    • -0
    • +1216
    ./AbstractMavenPublishJavaIntegTest.groovy
  1. … 5 more files in changeset.