Clone Tools
  • last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
Fix test

Simplify test

Configure source set to validate lazily

So that extension configuration has a chance to take effect.

  1. … 1 more file in changeset.
Rename and fix test

It doesn't matter how things are applied, we are testing the deprecated behavior here.

Remove unnecessary integration test

The only case tested here is already covered in AbstractPluginValidationIntegrationSpec.

Display nice type names consistently for validation warnings

Also use the new expectDeprecationWarning(String) to check for emitted runtime validation warnings.

  1. … 2 more files in changeset.
Consistently check for path sensitivity warnings during runtime

  1. … 13 more files in changeset.
Correctly report everything

  1. … 19 more files in changeset.
Correctly report everything

  1. … 19 more files in changeset.
Consolidate type validation

Use ValidateContext with a few standard implementations instead of the many different interfaces and implementations we used to collect valdiation problems before. This fixes issues with types being displayed inconsistently.

The implementation is not fully correct yet: we now fail to display the correct type for problems that are bound to a type instead of a property.

  1. … 46 more files in changeset.
Use nicer way to assert validation output

Remove unnecessary dependency

The plugin should apply it already.

Only test validating external types for static validation

Remove unnecessary test requirement

Migrate "reports conflicting types when property is replaced"

Migrate "can validate task classes using types from other projects"

Ensure that the validated task is executed, not that it's the only one

Migrate "can validate task classes using external types"

Migrate "detects annotations on setter methods"

Migrate "detects annotations on non-property methods"

Migrate "detects annotations on private getter methods"

Migrate "detects problems with file inputs"

Allow distinguishing between errors and warnings emitted in strict mode

Ensure that errors are actually reported

Fix runtime test case for validates task caching annotations

Migrate "report setters for property of mutable type #type"

Allow types to be reported sometimes for runtime warnings

Move "task cannot have property with annotation @#annotation.simpleName" back

We cannot even instantiate a task with the problems tested here during runtime.

There are tests for these cases in ArtifactTransformValuesInjectionIntegrationTest.

Migrate "does not report missing properties for Provider types"

Ensure that task being validated actually runs during test