[jira] [Commented] (MRELEASE-955) Document how to work with release profile in 3.x vs 2.x

["Konrad Windszus (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MRELEASE-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17491529#comment-17491529 ] 

Konrad Windszus commented on MRELEASE-955:
------------------------------------------

IMHO there is nothing speaking against using {{releaseProfiles}} already with Maven 3.x. Using the release profile during prepare feels weird to me and IMHO javadoc should rather be build with every (CI) build as it is often broken by commits.

> 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.1#820001)