[
https://issues.apache.org/jira/browse/MRELEASE-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17467415#comment-17467415
]
Rocher Suchard commented on MRELEASE-973:
-----------------------------------------
Hello,
I'd like first to comment this was not my issue: I simply commented with the
fact that [~rfscholte] reply can't work due to MRELEASE-1038
As I'm using the <releaseProfile> to enable gpg plugin, I can say this
alternative work and that I no longer have the "The requested profile "pom.xml"
could not be activated because it does not exist.".
=> For me, not from [~o.b.fischer] view point, the MRELEASE-1038 is fixed and
this one is fixed due to that.
Rocher
> 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)
