Skip to content

Provide a proper settings plugin instead of relying on a remote script #1

Open
@rnett

Description

@rnett

Applying a Gradle "plugin" via including a script (i.e. apply("some file") is frowned upon for a variety of reasons, including the lack of versioning, lack of dependency management (i.e. locking, or hosting in your own repository), and making build script compilation avoidance harder.

I don't see anything in your settings script that would be impossible to do via a settings plugin. For that matter, I don't see what value the settings plugin provides - it's easier and much better practice to just add the build plugin yourself.

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