Add warnings about the default value of maven.site.failonerror.
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@399789 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
da50cad575
commit
8970b82ce2
@ -27,7 +27,7 @@
|
||||
<action dev="aheritier" type="add">New property <code>maven.site.gunzip.options</code> can be used to set options when using gunzip (default value is -f).</action>
|
||||
<action dev="ltheussl" type="fix" issue="MPSITE-40">Missing <code>maven.ssh.args</code> in <code>site:publish</code>.</action>
|
||||
<action dev="aheritier" type="fix" issue="MPSITE-39">Deploy site on unix create rights rwxr-xr-x. Group members can't override files. The default value for <code>maven.site.chmod.mode</code> is now <code>775</code>.</action>
|
||||
<action dev="aheritier" type="add" issue="MPSITE-34">New property <code>maven.site.failonerror</code> can be used to bypass remote errors.</action>
|
||||
<action dev="aheritier" type="add" issue="MPSITE-34">New property <code>maven.site.failonerror</code> can be used to bypass remote errors. Defaults to <code>true</code>. <strong>*NOTE*</strong> that this default will fail a deploy for any "minor" error, please read the properties documentation.</action>
|
||||
<action dev="ltheussl" type="add" issue="MPSITE-31">Make <code>chmod</code> options in <code>site:sshdeploy</code> configurable.</action>
|
||||
<action dev="ltheussl" type="fix" issue="MPSITE-24" due-to="Julian Dunn">SSH arguments not used in <code>sshdeploy</code> with 'clean'.</action>
|
||||
<action dev="aheritier" type="fix" issue="MPSITE-28" due-to="Davy Toch">Deploying the site documentation through SSH always results in 'Build Successful'.</action>
|
||||
|
||||
@ -186,8 +186,14 @@
|
||||
<td>maven.site.failonerror</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Specifies if remote commands errors must stop the build.
|
||||
Specifies if errors in remote commands should stop the build.
|
||||
Defaults to <code>true</code>.
|
||||
<strong>NOTE</strong> that with this default, a remote deploy will
|
||||
fail for any "minor" error: for example if <code>tar</code> can't
|
||||
overwrite a file or if the remote user doesn't have the needed rights
|
||||
to change the permission for the root site directory
|
||||
(like for the <code>htdocs</code> dir on sourceforge).
|
||||
Sourceforge users are therefore advised to set this to <code>false</code>.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user