Skip to content

task-based configuration #17

@MattSturgeon

Description

@MattSturgeon

Plugins & extensions are great for setting up common defaults and simple scenarios, but ideally everything set by the gradle extension should map to a task property.

By introducing a common base class with shared configuration, and moving task-specific options to task properties you enable users to:

  • introduce their own custom tasks
  • have multiple instances of a task type
  • configure/override properties in the task rather than the plugin-extension

Like #13, this might be best approached as part of a major release as breaking changes may make sense.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions