Re: svn commit: r1747802 - in /maven/release/trunk/maven-release-plugin/src: it/projects/perform/MRELEASE-459/pom.xml main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java

> > Therefore, it is a change in a major version. Sure, but that's not the problem I see. I think we're moving away from convention over configuration as there is now no default release profile but the end user needs to configure one. Not too happy about that. > Do you care to create an issue

Re: svn commit: r1747802 - in /maven/release/trunk/maven-release-plugin/src: it/projects/perform/MRELEASE-459/pom.xml main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java

Am 2016-06-13 um 15:47 schrieb Anders Hammar: On Sat, Jun 11, 2016 at 5:46 PM, Michael Osipov wrote: Am 2016-06-11 um 15:25 schrieb Anders Hammar: Even if this (breaking) change is for v3.0.0 of the plugin, I'm missing some clear docs about how it is supposed to work

Re: svn commit: r1747802 - in /maven/release/trunk/maven-release-plugin/src: it/projects/perform/MRELEASE-459/pom.xml main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java

On Sat, Jun 11, 2016 at 5:46 PM, Michael Osipov wrote: > Am 2016-06-11 um 15:25 schrieb Anders Hammar: > >> Even if this (breaking) change is for v3.0.0 of the plugin, I'm missing >> some clear docs about how it is supposed to work from now on. Specifically >> for the plugin

Re: svn commit: r1747802 - in /maven/release/trunk/maven-release-plugin/src: it/projects/perform/MRELEASE-459/pom.xml main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java

Am 2016-06-11 um 15:25 schrieb Anders Hammar: Even if this (breaking) change is for v3.0.0 of the plugin, I'm missing some clear docs about how it is supposed to work from now on. Specifically for the plugin I assume that the idea is that the release profile to use should be specified

Re: svn commit: r1747802 - in /maven/release/trunk/maven-release-plugin/src: it/projects/perform/MRELEASE-459/pom.xml main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java

Well I always end up with multiple release profiles because different orgs need different GPG signing keys etc... On Saturday, 11 June 2016, Anders Hammar wrote: > Even if this (breaking) change is for v3.0.0 of the plugin, I'm missing > some clear docs about how it is

Re: svn commit: r1747802 - in /maven/release/trunk/maven-release-plugin/src: it/projects/perform/MRELEASE-459/pom.xml main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java

Even if this (breaking) change is for v3.0.0 of the plugin, I'm missing some clear docs about how it is supposed to work from now on. Specifically for the plugin I assume that the idea is that the release profile to use should be specified explicitly? Also, if the releaseProfile in the super-POM

Re: svn commit: r1747802 - in /maven/release/trunk/maven-release-plugin/src: it/projects/perform/MRELEASE-459/pom.xml main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java

Ah sorry... did saw this issue is already scheduled on 3.0... Kind regards Karl Heinz On 6/11/16 9:00 AM, Karl Heinz Marbaise wrote: Hi, This will break backward compatibility in a minor version which is not a good idea..This something for 3.0.0 Marking as deprecated good idea...but

Re: svn commit: r1747802 - in /maven/release/trunk/maven-release-plugin/src: it/projects/perform/MRELEASE-459/pom.xml main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java

Hi, This will break backward compatibility in a minor version which is not a good idea..This something for 3.0.0 Marking as deprecated good idea...but changing the default...Hm.. Kind regards Karl Heinz Marbaise On 6/10/16 11:20 PM, micha...@apache.org wrote: Author: michaelo Date: