Thanks for the clarification!
I will leave it as-is.
Michael
Am 2016-05-29 um 11:14 schrieb Christopher:
For what it's worth, they are *not* equivalent:
The <releaseProfiles /> element only applies to the release:perform goal,
not the release:prepare goal. <arguments />, on the other hand gets used by
both goals.
Thus, the ASF parent has activated the apache-release profile on both
goals, and the Maven parent only activates it for the release:perform goal,
presumably to save on some additional work during the preparation step
(speculation) at the possible cost of delayed notification of problems
which might arise in executing the plugins in that profile.
On Sat, May 28, 2016 at 5:19 AM Hervé BOUTEMY <herve.bout...@free.fr> wrote:
+1
Regards,
Hervé
Le samedi 28 mai 2016 00:42:00 Michael Osipov a écrit :
Hi folks,
I just have noticed that ASF Parent says:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.5.3</version>
<configuration>
...
<arguments>-Papache-release ${arguments}</arguments>
..
</configuration>
</plugin>
and Maven Parent:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
...
<releaseProfiles>apache-release</releaseProfiles>
...
<arguments>${arguments}</arguments>
</configuration>
</plugin>
Both seem equivalent to me. it safe to remove those two properties from
Maven Parent?
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
