Skip to content

Created gradle configurations aren't correctly configured #163

@timocov

Description

@timocov

According to official gradle docs https://docs.gradle.org/current/userguide/declaring_configurations.html#sec:configuration-flags-roles:

Out of canBeResolved, canBeConsumed and canBeDeclared flags "Configurations should only have one of these flags enabled.". When configurations get created in

Configuration smithyBuildConfig = configurations.maybeCreate(
SmithyUtils.getSmithyBuildConfigurationName(sourceSet));
smithyBuildConfig.setVisible(false);
smithyBuildConfig.setTransitive(true);
smithyBuildConfig.extendsFrom(configurations.getByName(compileOnlyConfigurationName));
smithyBuildConfig.setDescription("Build-time smithy dependencies for " + sourceSet + ".");
they don't have these flags configured, which means that by default they have all 3 flags set to true (according the gradle's source code).

It feels like smithyBuild configurations should be only marked as canBeResolved and all other flags should be set to false?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions