07-fine-grained-dm-apis

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Use underscore instead of dash in doc files

This is for consistency, and to reduce the risks of SEO

(because URLs would change).

  1. … 31 more files in changeset.
Fix include levels

  1. … 5 more files in changeset.
Fix include levels

  1. … 5 more files in changeset.
Fix include levels

  1. … 5 more files in changeset.
Fix include levels

  1. … 5 more files in changeset.
Fix include levels

  1. … 5 more files in changeset.
Fix include levels

  1. … 5 more files in changeset.
Fix include levels

  1. … 5 more files in changeset.
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.

  1. … 7 more files in changeset.
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.

  1. … 7 more files in changeset.
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.

  1. … 7 more files in changeset.
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.

  1. … 7 more files in changeset.
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.

  1. … 7 more files in changeset.
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.

  1. … 7 more files in changeset.
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.

  1. … 7 more files in changeset.
Reshuffle dependency management docs

This commit reshuffle existing dependency management docs

into the new dependency management chapter. It's worth noting

that there's no new content at this point, nor any effort to

make it consistent. It just moves things around, and there

are still quite a few places where dependency management docs

are found.

It doesn't try to fix dead links either.

  1. … 44 more files in changeset.
Reshuffle dependency management docs

This commit reshuffle existing dependency management docs

into the new dependency management chapter. It's worth noting

that there's no new content at this point, nor any effort to

make it consistent. It just moves things around, and there

are still quite a few places where dependency management docs

are found.

It doesn't try to fix dead links either.

  1. … 46 more files in changeset.
Reshuffle dependency management docs

This commit reshuffle existing dependency management docs

into the new dependency management chapter. It's worth noting

that there's no new content at this point, nor any effort to

make it consistent. It just moves things around, and there

are still quite a few places where dependency management docs

are found.

It doesn't try to fix dead links either.

    • -0
    • +250
    ./artifact-transforms.adoc
    • -0
    • +72
    ./fine-grained-dm-apis.adoc
    • -0
    • +59
    ./variant-aware-plugins.adoc
  1. … 38 more files in changeset.
Reshuffle dependency management docs

This commit reshuffle existing dependency management docs

into the new dependency management chapter. It's worth noting

that there's no new content at this point, nor any effort to

make it consistent. It just moves things around, and there

are still quite a few places where dependency management docs

are found.

It doesn't try to fix dead links either.

  1. … 44 more files in changeset.
Reshuffle dependency management docs

This commit reshuffle existing dependency management docs

into the new dependency management chapter. It's worth noting

that there's no new content at this point, nor any effort to

make it consistent. It just moves things around, and there

are still quite a few places where dependency management docs

are found.

It doesn't try to fix dead links either.

  1. … 44 more files in changeset.
Reshuffle dependency management docs

This commit reshuffle existing dependency management docs

into the new dependency management chapter. It's worth noting

that there's no new content at this point, nor any effort to

make it consistent. It just moves things around, and there

are still quite a few places where dependency management docs

are found.

It doesn't try to fix dead links either.

  1. … 44 more files in changeset.
Reshuffle dependency management docs

This commit reshuffle existing dependency management docs

into the new dependency management chapter. It's worth noting

that there's no new content at this point, nor any effort to

make it consistent. It just moves things around, and there

are still quite a few places where dependency management docs

are found.

It doesn't try to fix dead links either.

  1. … 44 more files in changeset.
Reshuffle dependency management docs

This commit reshuffle existing dependency management docs

into the new dependency management chapter. It's worth noting

that there's no new content at this point, nor any effort to

make it consistent. It just moves things around, and there

are still quite a few places where dependency management docs

are found.

It doesn't try to fix dead links either.

    • -0
    • +252
    ./artifact-transforms.adoc
    • -0
    • +72
    ./fine-grained-dm-apis.adoc
    • -0
    • +59
    ./variant-aware-plugins.adoc
  1. … 46 more files in changeset.