Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fixes.

  1. … 14 more files in changeset.
Fixes.

  1. … 14 more files in changeset.
Fixes.

  1. … 14 more files in changeset.
Fixes.

  1. … 14 more files in changeset.
Fixes.

  1. … 14 more files in changeset.
Fixes.

  1. … 14 more files in changeset.
Address compiler warnings in 'logging' subproject

    • -2
    • +2
    ./AbstractStyledTextOutputFactory.java
  1. … 5 more files in changeset.
Address compiler warnings in 'logging' subproject

    • -2
    • +2
    ./AbstractStyledTextOutputFactory.java
  1. … 5 more files in changeset.
Address compiler warnings in 'logging' subproject

    • -2
    • +2
    ./AbstractStyledTextOutputFactory.java
  1. … 5 more files in changeset.
Activate 'strict-compile' for all subprojects

    • -2
    • +2
    ./AbstractStyledTextOutputFactory.java
  1. … 148 more files in changeset.
Fall back to plain console with colors when console width is not known

    • -2
    • +5
    ./StreamBackedStandardOutputListener.java
  1. … 6 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

  1. … 20 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

  1. … 20 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

  1. … 35 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

  1. … 35 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

  1. … 35 more files in changeset.
When a property has no value, include the chain of properties from which the value is derived in the error message.

This is intended to help with diagnostics, as the user can see where the value should have come from. In this change, the diagnostics only works when `Property<T>` instances are connected together directly, stopping at the first `Provider<T>` which is not such a type.

  1. … 35 more files in changeset.
Add information about paths to dependencies when failing verification

When dependency verification fails, it's often necessary to actually

look at the artifacts which were downloaded. Gradle will not display

the paths to the artifacts which were involved in a verification

failure, so that the user can check if they are the ones they expect

or something else.

This also gives the ability to actually delete the file from the

local cache if it makes sense.

  1. … 13 more files in changeset.
Add information about paths to dependencies when failing verification

When dependency verification fails, it's often necessary to actually

look at the artifacts which were downloaded. Gradle will not display

the paths to the artifacts which were involved in a verification

failure, so that the user can check if they are the ones they expect

or something else.

This also gives the ability to actually delete the file from the

local cache if it makes sense.

  1. … 13 more files in changeset.
Add information about paths to dependencies when failing verification

When dependency verification fails, it's often necessary to actually

look at the artifacts which were downloaded. Gradle will not display

the paths to the artifacts which were involved in a verification

failure, so that the user can check if they are the ones they expect

or something else.

This also gives the ability to actually delete the file from the

local cache if it makes sense.

  1. … 13 more files in changeset.
Add information about paths to dependencies when failing verification

When dependency verification fails, it's often necessary to actually

look at the artifacts which were downloaded. Gradle will not display

the paths to the artifacts which were involved in a verification

failure, so that the user can check if they are the ones they expect

or something else.

This also gives the ability to actually delete the file from the

local cache if it makes sense.

  1. … 13 more files in changeset.
Add information about paths to dependencies when failing verification

When dependency verification fails, it's often necessary to actually

look at the artifacts which were downloaded. Gradle will not display

the paths to the artifacts which were involved in a verification

failure, so that the user can check if they are the ones they expect

or something else.

This also gives the ability to actually delete the file from the

local cache if it makes sense.

  1. … 13 more files in changeset.
Catch up with master

  1. … 415 more files in changeset.
Fix for error message formatting.

  1. … 4 more files in changeset.
Improve the formatting of user provided values and types in several error messages.

Change some more exceptions to use `TreeFormatter` to take care of the formatting of these things.

  1. … 6 more files in changeset.
Improve the formatting of user provided values and types in several error messages.

Change some more exceptions to use `TreeFormatter` to take care of the formatting of these things.

  1. … 6 more files in changeset.
Improve the formatting of user provided values and types in several error messages.

Change some more exceptions to use `TreeFormatter` to take care of the formatting of these things.

  1. … 2 more files in changeset.
Improve the formatting of user provided values and types in several error messages.

Change some more exceptions to use `TreeFormatter` to take care of the formatting of these things.

  1. … 6 more files in changeset.
Improve the formatting of user provided values and types in several error messages.

Change some more exceptions to use `TreeFormatter` to take care of the formatting of these things.

  1. … 6 more files in changeset.
Fixes.

  1. … 24 more files in changeset.