svn commit: r735762 - /maven/site/trunk/src/site/apt/guides/mini/guide-attached-tests.apt

[be...@apache.org]

Author: bentmann
Date: Mon Jan 19 09:59:37 2009
New Revision: 735762

URL: http://svn.apache.org/viewvc?rev=735762&view=rev
Log:
o Fixed guide about test JARs and added some more explanations

Modified:
    maven/site/trunk/src/site/apt/guides/mini/guide-attached-tests.apt

Modified: maven/site/trunk/src/site/apt/guides/mini/guide-attached-tests.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/mini/guide-attached-tests.apt?rev=735762&r1=735761&r2=735762&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/mini/guide-attached-tests.apt (original)
+++ maven/site/trunk/src/site/apt/guides/mini/guide-attached-tests.apt Mon Jan 19 09:59:37 2009
@@ -61,7 +61,7 @@
 * Using the attached test JAR
 
  In order to use the attached test JAR that was created above you simply specify a dependency on the main
- artifact with a specified classifier of <<<tests>>>:
+ artifact with a specified type of <<<test-jar>>>:
 
 +----+
 
@@ -80,3 +80,10 @@
 </project>
 
 +----+
+
+ Note that previous editions of this guide suggested to use <<<\<classifier\>tests\</classifier\>>>> instead of
+ <<<\<type\>test-jar\</type\>>>>. While this currently works for some cases, it does not properly work during a
+ reactor build of the test JAR module and any consumer if a lifecycle phase prior to <<<install>>> is invoked. In such
+ a scenario, Maven will not resolve the test JAR from the output of the reactor build but from the local/remote
+ repository. Apparently, the JAR from the repositories could be outdated or completely missing, causing a build
+ failure (cf. {{{http://jira.codehaus.org/browse/MNG-2045}MNG-2045}}).