[GitHub] [maven-release] nielsbasjes opened a new pull request #101: [MRELEASE-1077] Support for specifying profiles that can be activated during the prepare phase.

[GitBox <gi...@apache.org>]

nielsbasjes opened a new pull request #101:
URL: https://github.com/apache/maven-release/pull/101


   In some of my projects I have the website for the project as part of the code base.
   In those situations I want the website to show the latest released version of the project (I.e. not the current SNAPSHOT that is in the current code base).
   
   To allow updating this version in my website automatically as part of the release process; I would like to have a way to activate the relevant plugins only during the prepare phase of the new release so that I can run the appropriate scripts to change the website.
   
   The implementation is incredibly simple: I only had to attach the getAdditionalProfiles() for the PrepareReleaseMojo to a property. Most of the code is a new integration test.
   
   Following this checklist to help us incorporate your 
   contribution quickly and easily:
   
    - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MRELEASE-1077) filed 
          for the change (usually before you start working on it).  Trivial changes like typos do not 
          require a JIRA issue.  Your pull request should address just this issue, without 
          pulling in other changes.
    - [X] Each commit in the pull request should have a meaningful subject line and body.
    - [X] Format the pull request title like `[MJAVADOC-XXX] - Fixes bug in ApproximateQuantiles`,
          where you replace `MJAVADOC-XXX` with the appropriate JIRA issue. Best practice
          is to use the JIRA issue title in the pull request title and in the first line of the 
          commit message.
    - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    - [x] Run `mvn clean verify -Prun-its` to make sure basic checks pass. A more thorough check will 
          be performed on your pull request automatically.
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under 
   the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
    - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
    - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
      I'm already PMC for Apache Avro and comitter for Apache Flink
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org