You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by bu...@apache.org on 2017/11/11 13:05:54 UTC
svn commit: r1020692 - in /websites/staging/maven/trunk/content: ./
maven-site-1.0-site.jar run-maven/index.html
Author: buildbot
Date: Sat Nov 11 13:05:53 2017
New Revision: 1020692
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/maven-site-1.0-site.jar
websites/staging/maven/trunk/content/run-maven/index.html
Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Nov 11 13:05:53 2017
@@ -1 +1 @@
-1814948
+1814949
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
Modified: websites/staging/maven/trunk/content/run-maven/index.html
==============================================================================
--- websites/staging/maven/trunk/content/run-maven/index.html (original)
+++ websites/staging/maven/trunk/content/run-maven/index.html Sat Nov 11 13:05:53 2017
@@ -172,7 +172,7 @@ from the specified remote repositories:
<p>In other cases, it may be an incorrectly declared dependency (like the typo in the example above) which the project would need to fix, like a compilation error.</p></div>
<div class="section">
<h4><a name="Inconsistent_output"></a>Inconsistent output</h4>
-<p>Most plugins are optimized to know if they have to execute their task. In some cases the output can be polluted from a previous build and the end result is not what you exected. In such rare situations you can call the goal <tt>clean</tt> which means: remove the output directory. You can also call it as <tt>mvn clean verify</tt> which means: first clean up the output directory, next build the project and verify the outcome.</p></div></div></div>
+<p>Most plugins are optimized to know if they have to execute their task. In some cases the output can be polluted from a previous build and the end result is not what you expected. In such rare situations you can call the <tt>clean</tt> phase which means: remove the output directory. You can also call it as <tt>mvn clean verify</tt> which means: first clean up the output directory, next build the project and verify the outcome.</p></div></div></div>
</div>
</div>
</div>