You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (Jira)" <ji...@apache.org> on 2022/02/13 06:41:00 UTC
[jira] [Updated] (MRELEASE-955) Document how to work with release profile
[ https://issues.apache.org/jira/browse/MRELEASE-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated MRELEASE-955:
-----------------------------------
Description:
In v3.0.0 of the plugin the {{useReleaseProfile}} parameter has been deprecated (*and default value changed to {{false}}*).
This effectively changes from convention over configuration with a default release profile (the {{release-profile}} profile in the super-POM) so that the end user now needs:
1. to create a release profile (with his own naming choice)
2. and configure the plugin to use it (like add {{<arguments>-Pname_of_the_release_profile ...</arguments>}}).
We need to document this change in behavior as well as describe best-practice for handling this.
was:
In v3.0.0 of the plugin the {{useReleaseProfile}} parameter has been deprecated (and default value changed to {{false}}).
This effectively changes from convention over configuration with a default release profile (the {{release-profile}} profile in the super-POM) so that the end user now needs:
1. to create a release profile (with his own naming choice)
2. and configure the plugin to use it (like add {{<arguments>-Pname_of_the_release_profile ...</arguments>}}).
We need to document this change in behavior as well as describe best-practice for handling this.
> Document how to work with release profile
> -----------------------------------------
>
> Key: MRELEASE-955
> URL: https://issues.apache.org/jira/browse/MRELEASE-955
> Project: Maven Release Plugin
> Issue Type: Task
> Components: documentation
> Environment: n/a
> Reporter: Anders Hammar
> Priority: Major
>
> In v3.0.0 of the plugin the {{useReleaseProfile}} parameter has been deprecated (*and default value changed to {{false}}*).
> This effectively changes from convention over configuration with a default release profile (the {{release-profile}} profile in the super-POM) so that the end user now needs:
> 1. to create a release profile (with his own naming choice)
> 2. and configure the plugin to use it (like add {{<arguments>-Pname_of_the_release_profile ...</arguments>}}).
> We need to document this change in behavior as well as describe best-practice for handling this.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)