Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add tests that reproduce the problem: `ValidateTaskPropertiesIntegrationTest#reports mutable #type non-final fields`

Add tests that reproduce the problem: `ValidateTaskPropertiesIntegrationTest#reports mutable #type non-final fields`

Add tests that reproduce the problem: `ValidateTaskPropertiesIntegrationTest#reports mutable #type non-final fields`

Add tests that reproduce the problem: `ValidateTaskPropertiesIntegrationTest#reports mutable #type non-final fields`

Add tests that reproduce the problem: `ValidateTaskPropertiesIntegrationTest#report setters for property with mutable type #type`

Add tests that reproduce the problem: `ValidateTaskPropertiesIntegrationTest#reports mutable #type non-final fields`

Add tests that reproduce the problem: `ValidateTaskPropertiesIntegrationTest#reports mutable #type non-final fields`

Add tests that reproduce the problem: `ValidateTaskPropertiesIntegrationTest#reports mutable #type non-final fields`

Add tests that reproduce the problem: `ValidateTaskPropertiesIntegrationTest#report setters for property with mutable type #type`

Add tests that reproduce the problem: `ValidateTaskPropertiesIntegrationTest#report setters for property with mutable type #type`

Add tests that reproduce the problem: `ValidateTaskPropertiesIntegrationTest#reports mutable #type non-final fields`

Clean up `PropertyValidationAccess` to prepare it for the upcoming changes

Clean up `PropertyValidationAccess` to prepare it for the upcoming changes

Clean up `PropertyValidationAccess` to prepare it for the upcoming changes

Add `JavaReflectionUtil#getFieldOrNull` to help in Task field validation

Add integration tests for module metadata validation

Apply review suggestions to `Hashing`

Remove unused class

Remove unused class

Remove unused class

Validate mandatory attributes during parsing

If these attributes were missing, they caused a late error in the

ModuleMetadataSerializer (Cannot encode a null string). Now such

an error is reported directly during metadata parsing and the message

contains a path pointing at the problematic location in the JSON file.

Validate mandatory attributes during parsing

If these attributes were missing, they caused a late error in the

ModuleMetadataSerializer (Cannot encode a null string). Now such

an error is reported directly during metadata parsing and the message

contains a path pointing at the problematic location in the JSON file.

Cleanup module metadata parser code

- replace if-else-chains with switch

- consistent structure in methods

- Remove redundant type parameter

- Use UTF-8 constant

Cleanup module metadata parser code

- replace if-else-chains with switch

- consistent structure in methods

- Remove redundant type parameter

- Use UTF-8 constant

Avoid computing the same exclusion filter multiple times

A single edge can participate in different resolutions,

so it's a good thing to cache the exclusion filter for this

edge. Similarly, we may ask for the same node exclusions

multiple times, and it's a waste of time to rebuild the

filter, even if we have good optimizations below.

Avoid computing the same exclusion filter multiple times

A single edge can participate in different resolutions,

so it's a good thing to cache the exclusion filter for this

edge. Similarly, we may ask for the same node exclusions

multiple times, and it's a waste of time to rebuild the

filter, even if we have good optimizations below.

Avoid computing the same exclusion filter multiple times

A single edge can participate in different resolutions,

so it's a good thing to cache the exclusion filter for this

edge. Similarly, we may ask for the same node exclusions

multiple times, and it's a waste of time to rebuild the

filter, even if we have good optimizations below.

Unify 'VariantSpec' and 'VariantMetadataSpec'

These data structures in the test fixtures were very similar which

leads to duplication that needs to be maintained and changed in

parallel each time we extend/modify the expressiveness of variant

metadata.

Unify 'VariantSpec' and 'VariantMetadataSpec'

These data structures in the test fixtures were very similar which

leads to duplication that needs to be maintained and changed in

parallel each time we extend/modify the expressiveness of variant

metadata.

Raise accepted TAPI jar size by 2KB to enable new contributions