Author: buildbot
Date: Sat May 14 19:08:16 2016
New Revision: 988238
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/guides/development/guide-maven-development.html
websites/staging/maven/trunk/content/maven-site-1.0-site.jar
Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat May 14 19:08:16 2016
@@ -1 +1 @@
-1743850
+1743852
Modified:
websites/staging/maven/trunk/content/guides/development/guide-maven-development.html
==============================================================================
---
websites/staging/maven/trunk/content/guides/development/guide-maven-development.html
(original)
+++
websites/staging/maven/trunk/content/guides/development/guide-maven-development.html
Sat May 14 19:08:16 2016
@@ -457,22 +457,11 @@ Brett Porter" />
<p>When you find a issue you would like to work on add a comment in the issue
log so the core developers and other people looking for work know that someone
is already working on it.</p></div>
<div class="section">
<h3><a name="Wheres_the_source"></a>Where's the source?</h3>
-<p>See <a
href="/source-repository.html">http://maven.apache.org/source-repository.html</a>
for information. The Maven project uses a GIT for some things, and Subversion
for others, and this page tracks the situation.</p></div>
+<p>See <a
href="/source-repository.html">http://maven.apache.org/source-repository.html</a>
for information. The Maven project uses a Git for some things, and Subversion
for others, and this page tracks the situation.</p></div>
<div class="section">
<h3><a name="Dont_forget_tests"></a>Don't forget tests!</h3>
<p>You will find many unit tests in the maven-3 tree. If at all possible,
create or modify a unit test to demonstrate the problem, and then validate your
fix.</p>
-<p>If the problem case can't be set up in the unit tests, add an integration
test.</p>
-<p>Before submitting a patch, in any case, you should run all of the
integration tests. The tests require an empty local repository.</p>
-<p>Ant version 1.8+ is recommended.</p>
-<div class="source"><pre class="prettyprint linenums">cd maven
-export M2_HOME=/place-to-put-test-maven-root
-ant all (or with -Dmaven.home=/place-to-put-test-maven-root )
-cd ../maven-integration-testing
-rm -rf /tmp/it.repo
-/place-to-put-test-maven-root/bin/mvn -Prun-its -B -U clean install
-Dmaven.repo.local=/tmp/it.repo
-Dmaven.home=/place-to-put-test-maven-root</pre></div>
-<p>To run a single test, change the last command line to:</p>
-<div class="source"><pre class="prettyprint linenums">cd
../maven-integration-testing/core-it-suite
-[whatever]/mvn -Dtest=yourit [other options]</pre></div></div>
+<p>If the problem case can't be set up in the unit tests, add an integration
test. Before submitting a patch, in any case, you should run all of the
integration tests. The tests require an empty local repository. See <a
href="/core-its/core-it-suite/">Core IT Suite documentation</a> for more
details.</p></div>
<div class="section">
<h3><a name="Creating_and_submitting_a_patch">Creating and submitting a
patch</a></h3>
<p>When you have either completed an issue or just want some feedback on the
work you have done, create a patch and attach the patch to the issue in
question. We have a couple of guidelines when creating patches:</p>
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
