Skip to content
This repository was archived by the owner on Oct 5, 2018. It is now read-only.
This repository was archived by the owner on Oct 5, 2018. It is now read-only.

Improve messaging when strategies are skipped #175

@javajon

Description

@javajon

Searching GitHub people are using a combination of Strategies like this:

release {
    grgit = new OpenOp(dir: '.').call()

    versionStrategy Strategies.FINAL
    versionStrategy Strategies.PRE_RELEASE
    defaultVersionStrategy Strategies.DEVELOPMENT
}

With: gradlew build
the jar produced has a developer formatted version as expected by the default versing strategy.

With:./gradlew release -Prelease.scope=major -Prelease.stage=final
the error message "Stage final is not one of [dev] allowed for strategy development." is presented.

How can these Strategies work together?

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions