Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow explicit configured plugins to execute on master as well #129

Merged
merged 1 commit into from
Apr 17, 2023
Merged

Allow explicit configured plugins to execute on master as well #129

merged 1 commit into from
Apr 17, 2023

Commits on Mar 9, 2022

  1. Extended the MasterPromoteExtension to not only retain the hardcoded … 

    …gitflow-helper-maven-plugin itself and the maven-deploy-plugin, or the plugins related to explicit supplied command-line goals, but also allow a project to configure additional plugins that may also execute on master/support.

This serves two cases:

1) It solves the issue e-gineering#127 (though admittedly it still would be more clean to be able to download the pom file from the release repo)
2) It can serve as a basic extension point to allow other "things" to happen on a master build, that are beyond the scope of deploying maven artifacts (ie have some antrun script run)
    @glimmerveen
    glimmerveen committed Mar 9, 2022
    Configuration menu
    Copy the full SHA
    735ec61 View commit details
    Browse the repository at this point in the history