In order to use the `unpublished` library as-is in a composite build, the composing build can explicitly declare the substitutions that it provides.

====

// support -flags, which prints a description of its flags in JSON to
// stdout.

// vetTool specifies the vet command to run.
// Any tool that supports the (still unpublished) vet
// command-line protocol may be supplied; see
// golang.org/x/tools/go/analysis/unitchecker for one
// implementation. It is also used by tests.
//
// The default behavior (vetTool=="") runs 'go tool vet'.

 *
 * Most modification events may be published before or after a modification, so subscribers should not assume that the modification has or
 * hasn't happened yet. The reason for this design decision is that some of the underlying events (such as PSI tree changes) may be
 * published before or after a change, or even both. Modification events published before the modification should however be published close
 * to the modification.
 *

|`<dependencyManagement>` dependencies
|Not published
|Gradle dependency constraints are _transitive_, while Maven's dependency management block _isn't_

|<<rich_versions.adoc#rich-version-constraints,rich version constraints>>
|Publishes the _requires_ version
|Published the _requires_ version
|

|<<component_capabilities.adoc#declaring-component-capabilities,component capabilities>>
|Not published
|Not published

    /**
     * A comma separated list of public configurations in which this artifact is published.
     * The '*' wildcard is used to designate that the artifact is published in all public configurations.
     * A <code>null</code> value (the default) indicates that this artifact will be published without a conf attribute.
     * @return The value of 'conf' for this artifact.
     */
    @Nullable
    String getConf();

/**
 * Given a declared dependency to be published, determines the coordinates
 * that should be used to reference the dependency in published metadata. Dependencies
 * are resolved to component-level precision, meaning the coordinates of the resolved
 * variant's owning component are returned.
 */
public interface ComponentDependencyResolver {

    /**

        if (published.get(repositoryKey).contains(publicationWithProject)) {
            LOG.warn("Publication '" + projectIdentity + "' is published multiple times to the same location. It is likely that repository '" + repositoryName + "' is duplicated.");
            return;
        }

        for (PublicationWithProject previousPublicationWithProject : published.get(repositoryKey)) {

import org.gradle.api.artifacts.Configuration;

/**
 * A component which can declare additional variants corresponding to
 * features. When published to Maven POMs, the dependencies of those variants
 * are exposed as optional dependencies. When published to Gradle metadata, the
 * variants are published as is.
 *
 * @since 5.3
 */
public interface AdhocComponentWithVariants extends SoftwareComponent {

    /**

import javax.annotation.Nullable;

/**
 * Given a declared dependency to be published, determines the coordinates
 * that should be used to reference the dependency in published metadata. Dependencies
 * are resolved to variant-level precision, meaning that if resolved variant
 * is published to different coordinates than the declared component, the
 * variant coordinates are returned.
 *

     * similar to "test fixtures", but where the fixtures are consumed by the integration tests
     */
    @Unroll("can register integration test fixtures (published=#published, javadocs=#javadocs, sources=#sources)")
    def "can register integration test fixtures"() {
        buildFile << """
            sourceSets {
                integTestFixtures
            }