o clean up some poms

o record usage of support artifacts


git-svn-id: https://svn.apache.org/repos/asf/maven/core-integration-testing/trunk@468273 13f79535-47bb-0310-9956-ffa450edef68

its/core-integration-testing-support/1.3/pom.xml

@@ -26,7 +26,6 @@
     <relativePath>../../pom.xml</relativePath>    
   </parent>   
   <artifactId>maven-core-it-support</artifactId>
-  <packaging>jar</packaging>
   <version>1.3</version>
   <build>
     <plugins>

its/core-integration-testing-support/1.4/pom.xml

@@ -32,7 +32,7 @@
       <plugin>
         <groupId>org.apache.maven.its.plugins</groupId>
         <artifactId>maven-it-plugin-packaging</artifactId>
-        <version>1.0</version>
+        <version>1.0-SNAPSHOT</version>
         <extensions>true</extensions>
       </plugin>
     </plugins>

its/test.sh

@@ -10,7 +10,7 @@ OPTS="--settings settings.xml -Pmode-local-offline"
 # This will gather all the requirements for the integration tests. After downloading, build and
 # installing all the modules you should have a local repository with everything you need so that
 # you can work offline
-mvn --settings settings.xml install
+#mvn --settings settings.xml install
 
 # This should deploy all the integration testing artifacts into out filesystem-based, offline
 # remote repository. This is just sitting in your filesystem.
@@ -28,7 +28,7 @@ mvn $OPTS -f core-integration-testing-support/1.4/pom.xml deploy
 
 # Remove all integration testing artifacts that were installed in the local repository as many tests
 # download and verify the download.
-rm -rf /tmp/mits/repository-local/org/apache/maven/its
+#rm -rf /tmp/mits/repository-local/org/apache/maven/its
 
 # Now run the integration tests
-mvn $OPTS deploy
+#mvn $OPTS deploy

its/usage.txt

@@ -6,4 +6,10 @@ it0034: 1.4 (but uses a range to make sure the latest is nabbed)
 it0035: 1.1 and 1.1-old-location
 it0041: 1.2
 it0084: 1.3, 1.4 though no check is made for them in the IT
+        This uses commons-io, but create another artifact to use in this
+        test so that we don't have to depend on anything extneral.
+
+        1.3 also uses junit for some exclusion testing, again make something
+        ourselves for the test.
+
 it0092: 1.0-SNAPSHOT and we don't have this anywhere in source form, nice.