composite_builds.adoc

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Improve titles and structure based on feedback

  1. … 33 more files in changeset.
Move 'composite builds' into 'Authoring Gradle Builds' chapter

Composite builds are primarily a feature to organize your own

builds into multiple independent units.

They can be used to substitute a module dependency with a local

fork. Thus the chapter is now referenced from dependency management

in the section where we describe the different types of dependencies

that are supported.

    • -0
    • +217
    ./composite_builds.adoc
  1. … 10 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.

  1. … 48 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. … 40 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.

  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.

  1. … 40 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. … 35 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. … 33 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.

  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.

  1. … 48 more files in changeset.
Reword shared composite build between Gradle invocation limitation

Limitations on multiple composite builds with shared builds

Add additional limitations on the Gradle composite builds related to multiple composite builds referring

to the same shared builds.

Signed-off-by: Raman Gupta <rocketraman@gmail.com>

Composite build effect on configuration resolution

Since composite builds rely on dependency substitution they can have an

impact on _when_ configurations are resolved.

This is now better referenced in documentation.

Fixes #8174

Update release notes, user guide and samples to mention/demonstrate composite build support for `plugins { }` block. Add a Kotlin DSL variant of the 'plugins-dev' sample.

  1. … 62 more files in changeset.
De-incubate pre 4.0 things in userguide

and for command line arguments

  1. … 17 more files in changeset.
fix errors in composite_builds chapter

Signed-off-by: jnizet <jb@ninja-squad.com>

include Kotlin DSL sample for chapter composite_builds (multirepo-app sample)

Signed-off-by: jnizet <jb@ninja-squad.com>

  1. … 29 more files in changeset.
include Kotlin DSL sample for chapter composite_builds (declared-substitution sample)

Signed-off-by: jnizet <jb@ninja-squad.com>

  1. … 24 more files in changeset.
include Kotlin DSL sample for chapter composite_builds (basic sample)

Signed-off-by: jnizet <jb@ninja-squad.com>

  1. … 34 more files in changeset.
Convert user manual to be generated by Asciidoctor only

This change replaces all embedded Docbook syntax from the user manual.

Asciidoctor files are now converted directly to HTML and PDF.

It not only greatly simplifies the user manual generation pipeline, but also it makes it faster.

I did the following for all user manual pages:

- [x] Adjusted links to other manual pages, DSL docs, and Javadocs where necessary.

Fixed a couple dozen broken links at least.

- [x] Convert samples XML from docbook to asciidoctor syntax

- [x] Converted wide tables to a more flexible list-based display

Important contributor differences from now on:

- Users must use a `<file>.adoc#` prefix for all cross-reference links.

This is _required_ to achieve working links in all 3 outputs: multi-page user manual, single-page user manual, and PDF.

- The manual PDF is no longer themed, and no longer has the list of examples links in the TOC.

- File names were changed from camelCased to snake_case to have a crystal clear 1-1 mapping between source to output.

- Section reference verification is now handled by Asciidoctor verbose mode.

- The single-page user manual has the same navigation as the multi-page manual for now.

- [Common Asciidoctor extensions](https://github.com/gradle/dotorg-docs/tree/master/docs-asciidoctor-extensions) are now used by Gradle Guides and the User Manual, however, the the web assets (CSS, JS, etc) are not yet merged.

These extensions are responsible for injecting the navigation and styles.

The header/footer/navigation HTML can now be found under `subprojects/docs/src/main/resources`.

  1. … 401 more files in changeset.
Rename user manual asciidoc files to snake_case

This makes the file names match the output HTML file names,

allowing for us to convert the user manual to asciidoc only.

See also #5837

    • -0
    • +221
    ./composite_builds.adoc
  1. … 170 more files in changeset.