[
https://issues.apache.org/jira/browse/MRELEASE-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17491524#comment-17491524
]
Herve Boutemy edited comment on MRELEASE-955 at 4/23/22 3:02 PM:
-----------------------------------------------------------------
we can perhaps propose a first step = when upgrading to m-release-p 3.0,
propose users to configure useReleaseProfile explicitely to true (to override
default) if they don't want yet to create their own profile (and they don't use
Maven 4)
then, yes, in a second step with Maven 4 that removed the release-profile in
super POM MNG-7029, users will need to have their own profile (with proper
configuration for Maven Central requirements, for example)
the maven-release-plugin can then fail if Maven 4 is used and
useReleaseProfile=true = something we can implement in M6
WDYT?
was (Author: hboutemy):
we can perhaps propose a first step = when upgrading to m-release-p 3.0,
configure useReleaseProfile explicitely to true (to override default)
then, yes, in a second step with Maven 4 that removed the release-profile in
super POM MNG-7029, users will need to have their own profile (with proper
configuration for Maven Central requirements, for example)
the maven-release-plugin can then fail if Maven 4 is used and
useReleaseProfile=true = something we can implement in M6
WDYT?
> Document how to work with release profile in 3.x vs 2.x
> -------------------------------------------------------
>
> Key: MRELEASE-955
> URL: https://issues.apache.org/jira/browse/MRELEASE-955
> Project: Maven Release Plugin
> Issue Type: Task
> Components: documentation
> Affects Versions: 3.0.0-M1, 3.0.0-M5
> Environment: n/a
> Reporter: Anders Hammar
> Priority: Major
> Fix For: 3.0.0-M6
>
>
> 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.7#820007)
