Hopefully fix the nightly Maven build:

- The artifact creation never "installed" the artifacts in the local repository, so the validate task depended on downloading them -> which was wrong.
- The jenkins-maven-nightly target now runs actually 2 builds: One that deploys to apache repo using ANT, installs locally and validates the artifacts with the locally installed versions; after that it runs the maven-based build with "mvn"

git-svn-id: https://svn.apache.org/repos/asf/lucene/dev/trunk@1420677 13f79535-47bb-0310-9956-ffa450edef68

build.xml

@@ -368,7 +368,19 @@
   <!-- Jenkins tasks -->
   <target name="jenkins-hourly" depends="clean,test-with-heapdumps,validate,documentation-lint,jar-checksums,check-svn-working-copy"/>
   
-  <target name="jenkins-maven-nightly" depends="clean,remove-maven-artifacts,generate-maven-artifacts,run-maven-build"/>
+  <target name="jenkins-maven-nightly" depends="clean">
+    <!-- step 1: build, install, deploy, and validate ANT-generated maven artifacts: -->
+    <antcall>
+      <target name="remove-maven-artifacts"/>
+      <!-- this implicitely publishes the maven artifacts: -->
+      <target name="validate-maven-dependencies"/>
+    </antcall>
+    <!-- step 2: run the maven build to check that the pom templates also work to drive "mvn": -->
+    <antcall>
+      <target name="remove-maven-artifacts"/>
+      <target name="run-maven-build"/>
+    </antcall>
+  </target>
   
   <target name="jenkins-clover" depends="run-clover"/>
 </project>

lucene/common-build.xml

@@ -475,6 +475,10 @@
       <artifact:install-provider artifactId="wagon-ssh" version="1.0-beta-7"/>
       <parent-poms/>
       <artifact:pom id="maven.project" file="@{pom.xml}"/>
+      <artifact:install file="@{jar.file}">
+        <artifact-attachments/>
+        <pom refid="maven.project"/>
+      </artifact:install>
       <artifact:deploy file="@{jar.file}">
         <artifact-attachments/>
         <remoteRepository id="${m2.repository.id}" url="${m2.repository.url}">