org.gradle.api.component.ConfigurationVariantDetails Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of gradle-api Show documentation

Gradle 6.9.1 API redistribution.

There is a newer version: 8.11.1

/*
 * Copyright 2019 the original author or authors.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package org.gradle.api.component;

import org.gradle.api.artifacts.ConfigurationVariant;
import org.gradle.internal.HasInternalProtocol;

/**
 * The details object used to determine what to do with a
 * configuration variant when publishing.
 * 
 * This type also contains Maven specific information used to map the variant to a Maven POM file.
 *
 * @since 5.3
 */
@HasInternalProtocol
public interface ConfigurationVariantDetails {
    /**
     * The configuration variant
     */
    ConfigurationVariant getConfigurationVariant();

    /**
     * Marks this configuration variant as being skipped when publishing.
     */
    void skip();

    /**
     * Provides information about the optional status of this added configuration variant.
     *
     * 

     *     For the Maven world, this means that dependencies will be declared as {@code optional}.
     *     For the Ivy world, this means that configuration marked optional will not be extended by the {@code default} configuration.
     * 
     */
    void mapToOptional();

    /**
     * Provides information about how to publish to a Maven POM file. If
     * nothing is said, Gradle will publish all dependencies from this
     * configuration to the compile scope. It is preferable to give
     * a mapping in order for consumers to get the right dependencies when
     * asking for the API or the runtime of a component published as a POM
     * file only.
     *
     * Note that Gradle will write Maven scopes in the following order:
     *
     * 
     *     compile dependencies
     *     runtime dependencies
     *     optional compile dependencies
     *     optional runtime dependencies
     * 
     *
     * The mapping only applies to dependencies: dependency constraints will
     * systematically be published as import scope.
     *  @param scope the Maven scope to use for dependencies found in this configuration variant
     *
     */
    void mapToMavenScope(String scope);
}