StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
@RequiredFeature can be used as a repeated annotation

If used for a single feature, avoid annotation noise by not using the

composite annotation. This also avoids the confusion that the

@RequiredFeature annotation cannot be used independently

(no compile error but does not work).

I made the @RequiredFeatures annotation package-private as it is

only required by the compiler and the runner now.

Signed-off-by: Benjamin Muskalla <bmuskalla@gradle.com>

    • -4
    • +1
    ./StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
  1. … 43 more files in changeset.
@RequiredFeature can be used as a repeated annotation

If used for a single feature, avoid annotation noise by not using the

composite annotation. This also avoids the confusion that the

@RequiredFeature annotation cannot be used independently

(no compile error but does not work).

I made the @RequiredFeatures annotation package-private as it is

only required by the compiler and the runner now.

Signed-off-by: Benjamin Muskalla <bmuskalla@gradle.com>

    • -4
    • +1
    ./StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
  1. … 43 more files in changeset.
Remove trailing space in error message

And pay the price with tons of whitespace changes...

    • -19
    • +19
    ./StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
  1. … 10 more files in changeset.
Remove trailing space in error message

And pay the price with tons of whitespace changes...

    • -19
    • +19
    ./StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
  1. … 9 more files in changeset.
Remove trailing space in error message

And pay the price with tons of whitespace changes...

    • -19
    • +19
    ./StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
  1. … 10 more files in changeset.
Remove trailing space in error message

And pay the price with tons of whitespace changes...

    • -19
    • +19
    ./StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
  1. … 10 more files in changeset.
Remove trailing space in error message

And pay the price with tons of whitespace changes...

    • -19
    • +19
    ./StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
  1. … 10 more files in changeset.
Remove trailing space in error message

And pay the price with tons of whitespace changes...

    • -19
    • +19
    ./StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
  1. … 10 more files in changeset.
Revert "Do not emit deprecation warning for deprecated 'force'"

This reverts commit 1db54192db6ef9af5c2fd6b227004eed9a27c07f.

    • -0
    • +1
    ./StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
  1. … 10 more files in changeset.
Do not emit deprecation warning for deprecated 'force'

Nagging for this deprecation will only start with 6.1 to ease

the migration from 'force' to 'strictly'.

    • -1
    • +0
    ./StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
  1. … 10 more files in changeset.
Do not emit deprecation warning for deprecated 'force'

Nagging for this deprecation will only start with 6.1 to ease

the migration from 'force' to 'strictly'.

    • -1
    • +0
    ./StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
  1. … 10 more files in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions() (#10755)

This name change more clearly communicates the semantics of the

feature from a users point of view.

This commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

would have been misleading in the future. To make sure we catch all,

this also updates all variable/method/package names.

    • -0
    • +507
    ./StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
  1. … 70 more files in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions()

This is more clearly communicating the semantics of the feature

from a users point of view.

The commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

will be misleading in the future. To make sure we catch all,

I also updated all variable/method/package names.

    • -0
    • +507
    ./StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
  1. … 70 more files in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions()

This is more clearly communicating the semantics of the feature

from a users point of view.

The commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

will be misleading in the future. To make sure we catch all,

I also updated all variable/method/package names.

    • -0
    • +507
    ./StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
  1. … 70 more files in changeset.
Rename inheritStrictVersions() -> endorseStrictVersions()

This is more clearly communicating the semantics of the feature

from a users point of view.

The commit also removes all mentions of 'inheriting' AND 'forSubgraph'.

There have been some leftovers in documentation/comments that

will be misleading in the future. To make sure we catch all,

I also updated all variable/method/package names.

    • -0
    • +507
    ./StrictVersionConstraintsFeatureInteractionIntegrationTest.groovy
  1. … 70 more files in changeset.