gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Validate credential providers before task execution

  1. … 7 more files in changeset.
Validate credential providers before task execution

  1. … 7 more files in changeset.
Simplify usage of Property<Credentials> in AuthenticationSupporter

  1. … 8 more files in changeset.
Simplify usage of Property<Credentials> in AuthenticationSupporter

  1. … 10 more files in changeset.
Simplify usage of Property<Credentials> in AuthenticationSupporter

  1. … 10 more files in changeset.
Add input field Property<Credentials> to publishing tasks

This way the error messages coming from providers are not lost.

  1. … 2 more files in changeset.
Use Property<Credentials> in AuthenticationSupporter

For now, fail due to missing credentials at execution time and with error messages that we currently get.

  1. … 6 more files in changeset.
Add credentials provider for username and password credentials

Test the feature via publishing to Maven and Ivy repositories.

Do not add any public APIs at this point.

  1. … 11 more files in changeset.
Clean up maven publishing module

- use lambdas where possible

- remove declared but unthrown exceptions

- use diamond operator when instantiating generics

- try-with-resources

  1. … 8 more files in changeset.
Address compiler warnings in 'ivy' subproject

Address compiler warnings in 'ivy' subproject

Address compiler warnings in 'ivy' subproject

Use plugins DSL in Javadoc code snippets

    • -1
    • +3
    ./api/publish/ivy/IvyModuleDescriptorSpec.java
    • -12
    • +26
    ./api/publish/ivy/IvyPublication.java
  1. … 44 more files in changeset.
Use plugins DSL in Javadoc code snippets

    • -1
    • +3
    ./api/publish/ivy/IvyModuleDescriptorSpec.java
    • -12
    • +26
    ./api/publish/ivy/IvyPublication.java
  1. … 44 more files in changeset.
Revert "Configuration of build identifier"

This reverts commits ecb234a255f,

46d52bf8e7e10, 97e9694e12f.

  1. … 12 more files in changeset.
Revert "Make publication build identifier configurable"

This reverts commit ecb234a255f2af0abf9e06c282f9be4ee85d6014.

  1. … 8 more files in changeset.
Make publication build identifier configurable

This allows to set a user defined value or a constant in case that

information is not needed and having a stable .module output is

preferred.

Issue #11717

  1. … 8 more files in changeset.
Make publication build identifier configurable

This allows to set a user defined value or a constant in case that

information is not needed and having a stable .module output is

preferred.

Issue #11717

  1. … 8 more files in changeset.
Publication can configure the build identifier

This allows to use a user defined value or a constant in case that

information is not needed and having a stable .module output is

preferred.

Issue #11717

  1. … 7 more files in changeset.
Make publication build identifier configurable

This allows to set a user defined value or a constant in case that

information is not needed and having a stable .module output is

preferred.

Issue #11717

  1. … 8 more files in changeset.
Make publication build identifier configurable

This allows to set a user defined value or a constant in case that

information is not needed and having a stable .module output is

preferred.

Issue #11717

  1. … 8 more files in changeset.
Make publication build identifier configurable

This allows to set a user defined value or a constant in case that

information is not needed and having a stable .module output is

preferred.

Issue #11717

  1. … 7 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

  1. … 36 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

  1. … 46 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

  1. … 46 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

  1. … 46 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

  1. … 46 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

  1. … 45 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

  1. … 45 more files in changeset.
Improve variant matching error messages

Error messages prove to be difficult to interpret from a user point of

view. This commit tries to improve the situation by doing a couple of

things:

1. describing more clearly what the consumer is asking for. This includes,

when possible (currently only in the Java ecosystem), interpreting the

consumer attributes as a human-readable description, instead of a raw

list of attributes.

2. giving more context when possible. In particular, sometimes we fail

with an ambiguous variant error selection, but we only list the remaining

candidates, not listing the ones which were actually discarded during

selection. This proved to be particularly complex to debug from various

users (plugin authors and end-users).

  1. … 44 more files in changeset.