Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Use a flatten directory for all adoc files

This commit reworks how asciidoctor files are processed,

by allowing to structure docs using subdirectories, while

maintaining consistent locations for resources, images, samples,

...

This works by flattening all adoc files into a resources

directory before processing. It means that while we can

use a directory tree to organize docs, we must make sure

not to use the same file name twice.

This makes it possible to compose files more easily. For

example, the dependency management docs can be read as

a single file, or individual files, or as chapters.

Technically speaking, we could remove the "userguideSinglePage"

task, but it's kept just because it's significantly slower

to build.

Use a flatten directory for all adoc files

This commit reworks how asciidoctor files are processed,

by allowing to structure docs using subdirectories, while

maintaining consistent locations for resources, images, samples,

...

This works by flattening all adoc files into a resources

directory before processing. It means that while we can

use a directory tree to organize docs, we must make sure

not to use the same file name twice.

This makes it possible to compose files more easily. For

example, the dependency management docs can be read as

a single file, or individual files, or as chapters.

Technically speaking, we could remove the "userguideSinglePage"

task, but it's kept just because it's significantly slower

to build.

Use a flatten directory for all adoc files

This commit reworks how asciidoctor files are processed,

by allowing to structure docs using subdirectories, while

maintaining consistent locations for resources, images, samples,

...

This works by flattening all adoc files into a resources

directory before processing. It means that while we can

use a directory tree to organize docs, we must make sure

not to use the same file name twice.

This makes it possible to compose files more easily. For

example, the dependency management docs can be read as

a single file, or individual files, or as chapters.

Technically speaking, we could remove the "userguideSinglePage"

task, but it's kept just because it's significantly slower

to build.

Use a flatten directory for all adoc files

This commit reworks how asciidoctor files are processed,

by allowing to structure docs using subdirectories, while

maintaining consistent locations for resources, images, samples,

...

This works by flattening all adoc files into a resources

directory before processing. It means that while we can

use a directory tree to organize docs, we must make sure

not to use the same file name twice.

This makes it possible to compose files more easily. For

example, the dependency management docs can be read as

a single file, or individual files, or as chapters.

Technically speaking, we could remove the "userguideSinglePage"

task, but it's kept just because it's significantly slower

to build.

Use a flatten directory for all adoc files

This commit reworks how asciidoctor files are processed,

by allowing to structure docs using subdirectories, while

maintaining consistent locations for resources, images, samples,

...

This works by flattening all adoc files into a resources

directory before processing. It means that while we can

use a directory tree to organize docs, we must make sure

not to use the same file name twice.

This makes it possible to compose files more easily. For

example, the dependency management docs can be read as

a single file, or individual files, or as chapters.

Technically speaking, we could remove the "userguideSinglePage"

task, but it's kept just because it's significantly slower

to build.

Use a flatten directory for all adoc files

This commit reworks how asciidoctor files are processed,

by allowing to structure docs using subdirectories, while

maintaining consistent locations for resources, images, samples,

...

This works by flattening all adoc files into a resources

directory before processing. It means that while we can

use a directory tree to organize docs, we must make sure

not to use the same file name twice.

This makes it possible to compose files more easily. For

example, the dependency management docs can be read as

a single file, or individual files, or as chapters.

Technically speaking, we could remove the "userguideSinglePage"

task, but it's kept just because it's significantly slower

to build.

Use a flatten directory for all adoc files

This commit reworks how asciidoctor files are processed,

by allowing to structure docs using subdirectories, while

maintaining consistent locations for resources, images, samples,

...

This works by flattening all adoc files into a resources

directory before processing. It means that while we can

use a directory tree to organize docs, we must make sure

not to use the same file name twice.

This makes it possible to compose files more easily. For

example, the dependency management docs can be read as

a single file, or individual files, or as chapters.

Technically speaking, we could remove the "userguideSinglePage"

task, but it's kept just because it's significantly slower

to build.

Let tests use 'implementation' and 'testImplementation' configurations

As replacement for 'compile' and 'testCompile'.

  1. … 14 more files in changeset.
Let tests use 'implementation' and 'testImplementation' configurations

As replacement for 'compile' and 'testCompile'.

  1. … 14 more files in changeset.
Let tests use 'implementation' and 'testImplementation' configurations

As replacement for 'compile' and 'testCompile'.

  1. … 14 more files in changeset.
Let tests use 'implementation' and 'testImplementation' configurations

As replacement for 'compile' and 'testCompile'.

  1. … 14 more files in changeset.
Merge pull request #9528 from gradle/wolfs/scheduler/revert-completed-tracking

Revert PR #8715 for improving scheduler performance

Add more logging for node completion

Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

Accept deprecation warnings in IvyRemoteLegacyPublishIntegrationTest

Let Build Dashboard tests not use deprecated configurations

Let Build Dashboard tests not use deprecated configurations

Let Build Dashboard tests not use deprecated configurations

Let Build Dashboard tests not use deprecated configurations

Let EAR tests not use deprecated configurations

Let EAR tests not use deprecated configurations

Let EAR tests not use deprecated configurations

Let EAR tests not use deprecated configurations