svn commit: r798488 - /maven/core-integration-testing/trunk/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3023ReactorDependencyResolutionTest.java

[be...@apache.org]

Author: bentmann
Date: Tue Jul 28 11:19:02 2009
New Revision: 798488

URL: http://svn.apache.org/viewvc?rev=798488&view=rev
Log:
o Fixed/clarified pre-conditions

Modified:
    maven/core-integration-testing/trunk/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3023ReactorDependencyResolutionTest.java

Modified: maven/core-integration-testing/trunk/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3023ReactorDependencyResolutionTest.java
URL: http://svn.apache.org/viewvc/maven/core-integration-testing/trunk/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3023ReactorDependencyResolutionTest.java?rev=798488&r1=798487&r2=798488&view=diff
==============================================================================
--- maven/core-integration-testing/trunk/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3023ReactorDependencyResolutionTest.java (original)
+++ maven/core-integration-testing/trunk/core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3023ReactorDependencyResolutionTest.java Tue Jul 28 11:19:02 2009
@@ -113,8 +113,8 @@
      * location should be present in the compile classpath output from the 
      * maven-it-plugin-dependency-resolution:compile mojo execution.
      * 
-     * Afterwards, the a separate Maven call to the 'initialize' phase should succeed, since the
-     * dependency artifact has been installed locally. This second execution should use the jar file
+     * Afterwards, the projects are cleaned and a separate Maven call to the 'initialize' phase should succeed, since
+     * the dependency artifact has been installed locally. This second execution should use the jar file
      * from the local repository in its classpath output.
      */
     public void testitMNG3023C()
@@ -137,9 +137,7 @@
         assertTrue( compileClassPath.toString(), compileClassPath.contains( "dependency-1.jar" ) );
         assertFalse( compileClassPath.toString(), compileClassPath.contains( "dependency-classes" ) );
 
-        // The IT doesn't actually run the compiler but merely mimics its effect, i.e. the creation of the output dir
-        new File( testDir, "dependency/dependency-classes" ).mkdirs();
-        
+        verifier.deleteDirectory( "dependency/dependency-classes" );
         verifier.deleteDirectory( "consumer/target" );
         verifier.setLogFileName( "log-c-2.txt" );
         verifier.executeGoal( "validate" );