You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/04/15 09:46:00 UTC

[jira] [Comment Edited] (MRELEASE-973) Please keep the property performRelease or provide an alternative for it

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

Michael Osipov edited comment on MRELEASE-973 at 4/15/22 9:45 AM:
------------------------------------------------------------------

[~rocher.suchard], I will release 3.0.0-M2 this month.


was (Author: michael-o):
[~rocher.suchard], I will release 3.0.0-M2 this months.

> Please keep the property performRelease or provide an alternative for it
> ------------------------------------------------------------------------
>
>                 Key: MRELEASE-973
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-973
>             Project: Maven Release Plugin
>          Issue Type: Wish
>          Components: perform
>    Affects Versions: 3.0.0-M1
>            Reporter: Oliver B. Fischer
>            Priority: Critical
>              Labels: compatibility, feature
>             Fix For: waiting-for-feedback
>
>
> MRELEASE-896 deprecates the {{useReleaseProfile}} and changed its default value from {{true}} to {{false}}. 
> Unfortunately this disabled also the setting of the property {{performRelease}} which we use to enable multiple profiles during the release process.
> At least we need a possibility to enable multiple, sometimes different, profiles during a release and its preparation.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)