04-modeling-features

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
rework links to snippets

    • -20
    • +20
    ./cross_project_publications.adoc
  1. … 101 more files in changeset.
Fix documentation typos

Signed-off-by: Michael Ernst <mernst@cs.washington.edu>

  1. … 21 more files in changeset.
Fix typo in section on variants in user manual

Document source and javadoc jar for feature variants

Javadoc and source jars can be configured as well for feature variants.

This is now properly documented.

Issue #11140

  1. … 5 more files in changeset.
Document source and javadoc jar for feature variants

Javadoc and source jars can be configured as well for feature variants.

This is now properly documented.

Issue #11140

  1. … 5 more files in changeset.
Fix link in capabilities conflict handling section in documentation

Fix result of capabilities conflict

The documentation still used the old message / format

  1. … 2 more files in changeset.
Document default Gradle variant attributes

Fixes #10469

  1. … 2 more files in changeset.
'Understanding variant selection' and 'Declaring attributes' go together

  1. … 3 more files in changeset.
Improve titles and structure based on feedback

    • -0
    • +254
    ./artifact_transforms.adoc
  1. … 29 more files in changeset.
Split up section on 'features/variants'

Used 'Variants' in main titel, as this is the more common term

we use (as in variant-aware dependency management) and this chapter

bundles all things variant specific (like matching).

    • -0
    • +87
    ./component_capabilities.adoc
    • -0
    • +251
    ./cross_project_publications.adoc
  1. … 3 more files in changeset.
Split and sort 'controlling transitive versions'

  1. … 26 more files in changeset.
Rewrite section on component metadata rules (#10735)

The section was written when the very first version of rules was

introduced and since then only marginally updated.

This is a complete rewrite of the section focusing on explaining

all the metadata modeling features of Gradle Module Metadata

which can be utilized in rules to enrich existing metadata.

The features are described on using real-world use cases.

Related sections are also updated where applicable.

  1. … 58 more files in changeset.
Remove redundant section

Keep 'building' vs 'running' in feature variant chapter

improved confusing documentation and fixed odd grammar

Signed-off-by: Ross Goldberg <ross.goldberg@gmail.com>

Some text improvements

  1. … 2 more files in changeset.
Improve outgoing variant report

* Add capabilities information to the report

  1. … 2 more files in changeset.
Document variant reporting task

- Includes clarified documentation on usage of classes for java-library

projects.

  1. … 1 more file in changeset.
Document error handling for variant selection

  1. … 1 more file in changeset.
Merge pull request #10274 from gradle/jjohannes/gmm-by-default

Publish and use Gradle Module Metadata by default

  1. … 3 more files in changeset.
Consistent wording: 'Gradle Module Metadata' (not experimental)

  1. … 7 more files in changeset.
Rework declaring_dependencies.adoc

* Rework section levels

* Fill in missing content

* Moved the part about repository and metadata source to the

repositories document

  1. … 5 more files in changeset.
Rework section levels in controlling_transitive_dependencies.adoc

* Makes sure we have a sensible outline

* Update links from other pages to it

  1. … 6 more files in changeset.
Extract page about variant model

This will allow more focused linking and reading from other chapters.

    • -0
    • +187
    ./variant_model.adoc
  1. … 2 more files in changeset.
Reorganize Gradle Module Metadata spec documents

* Keep a 1.0 spec

* Add a latest spec, now at 1.1

* Update all links to point to latest spec

Proposal is that upon creation of 1.2, latest is copied with a 1.1 name

and then latest is edited to become 1.2.

This enables having a stable link for the latest version and historical

versions in direct access. Maintenance should be minimal as older

version have no reason to change anymore.

  1. … 4 more files in changeset.
Integrate review feedback about modeling features docs

Add short section about targetting different platforms

Add advanced example of producing a new variant

This example shows how to produce a new variant of a library that

can be used in a specific context from the consumer side. This

involves reusing existing attributes as well as defining compatibility

rules.

  1. … 24 more files in changeset.
Add section about cross-project publications

This commit introduces documentation explaining _one_ way to

perform safe, cross-project boundaries by exposing configurations

which are either consumable or resolvable.

It does _not_ explain the variant-aware version of this which

requires more ceremony.

  1. … 7 more files in changeset.