Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add Javadoc and Sources variants by default

This makes the Java (Library) plugin add these variants for the

main and for optional features.

- Separate 'javadoc' tasks are now automatically registered for

all optional features based on separate source sets

- jar tasks for Javadoc and Sources are registered for main source set

and each optional feature source set

- The variants are published via an opt-in on the plugin extension:

publishJavadocAndSources()

Add Javadoc and Sources variants by default

This makes the Java (Library) plugin add these variants for the

main and for optional features.

- Separate 'javadoc' tasks are now automatically registered for

all optional features based on separate source sets

- jar tasks for Javadoc and Sources are registered for main source set

and each optional feature source set

- The variants are published via an opt-in on the plugin extension:

publishJavadocAndSources()

Update KotlinDslScriptsModel javadoc

Signed-off-by: Paul Merlin <paul@gradle.com>

Update KotlinDslScriptsModel javadoc

Signed-off-by: Paul Merlin <paul@gradle.com>

Update KotlinDslScriptsModel javadoc

Signed-off-by: Paul Merlin <paul@gradle.com>

Update KotlinDslScriptsModel javadoc

Signed-off-by: Paul Merlin <paul@gradle.com>

Remove unnecessary test requirement

Add crude coverage for kotlin dsl scripts collection

Signed-off-by: Paul Merlin <paul@gradle.com>

Add crude coverage for kotlin dsl scripts collection

Signed-off-by: Paul Merlin <paul@gradle.com>

Add crude coverage for kotlin dsl scripts collection

Signed-off-by: Paul Merlin <paul@gradle.com>

Add crude coverage for kotlin dsl scripts collection

Signed-off-by: Paul Merlin <paul@gradle.com>

Temporarily enable leniency by default, for precompiled scripts support

Signed-off-by: Paul Merlin <paul@gradle.com>

Temporarily enable leniency by default, for precompiled scripts support

Signed-off-by: Paul Merlin <paul@gradle.com>

Temporarily enable leniency by default, for precompiled scripts support

Signed-off-by: Paul Merlin <paul@gradle.com>

Temporarily enable leniency by default, for precompiled scripts support

Signed-off-by: Paul Merlin <paul@gradle.com>

Naive implementation of precompiled scripts collection

Signed-off-by: Paul Merlin <paul@gradle.com>

Naive implementation of precompiled scripts collection

Signed-off-by: Paul Merlin <paul@gradle.com>

Naive implementation of precompiled scripts collection

Signed-off-by: Paul Merlin <paul@gradle.com>

Naive implementation of precompiled scripts collection

Signed-off-by: Paul Merlin <paul@gradle.com>

Let KotlinDslScriptsModelBuilder infer set of scripts when none given

Only settings and project scripts for now

Signed-off-by: Paul Merlin <paul@gradle.com>

Let KotlinDslScriptsModelBuilder infer set of scripts when none given

Only settings and project scripts for now

Signed-off-by: Paul Merlin <paul@gradle.com>

Let KotlinDslScriptsModelBuilder infer set of scripts when none given

Only settings and project scripts for now

Signed-off-by: Paul Merlin <paul@gradle.com>

Let KotlinDslScriptsModelBuilder infer set of scripts when none given

Only settings and project scripts for now

Signed-off-by: Paul Merlin <paul@gradle.com>

Use proper ID generation for test output progress events

Use proper ID generation for test output progress events

Use proper ID generation for test output progress events

Use proper ID generation for test output progress events

Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.

Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.

Improve error message when build fails because of missing metadata

Gradle 6.0 removed the "artifact" metadata source by default.

This means that if a module is published _only_ with an artifact,

previous version of Gradle would find it, but 6.0 would fail with

a module missing exception.

The problem is that it's hard to realize that the issue comes

from the change of this default artifact sources.

This commit tries to improve the situation by recognizing that

a failure is related to not finding metadata, and in this case

would suggest that if the metadata is missing, it is still

possible that the jar is present.

The drawback of this approach is that we're unsure: if, for

some reason, the module is _really_ absent, then we gave a

wrong advice. This means, in particular, in case of wrong

coordinates.