I think the "validate-maven-dependencies" should be directly after building the 
maven distribution, so maybe change to:
<target name="jenkins-maven-nightly" 
depends="clean,remove-maven-artifacts,generate-maven-artifacts,validate-maven-dependencies,run-maven-build"/>

But that’s minor, I just want to make sure that the maven-based build itself 
does not change the artifacts in local repo.

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [email protected]


> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Tuesday, December 11, 2012 10:24 PM
> To: [email protected]
> Subject: svn commit: r1420421 - /lucene/dev/trunk/build.xml
> 
> Author: sarowe
> Date: Tue Dec 11 21:23:32 2012
> New Revision: 1420421
> 
> URL: http://svn.apache.org/viewvc?rev=1420421&view=rev
> Log:
> jenkins-maven-nightly: deploy maven snapshots (via generate-maven-
> artifacts) before running tests under maven
> 
> Modified:
>     lucene/dev/trunk/build.xml
> 
> Modified: lucene/dev/trunk/build.xml
> URL:
> http://svn.apache.org/viewvc/lucene/dev/trunk/build.xml?rev=1420421&r1
> =1420420&r2=1420421&view=diff
> ==========================================================
> ====================
> --- lucene/dev/trunk/build.xml (original)
> +++ lucene/dev/trunk/build.xml Tue Dec 11 21:23:32 2012
> @@ -368,7 +368,7 @@
>    <!-- 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,run-maven-build,generate-maven-artifacts,validate-maven-
> dependencies"/>
> +  <target name="jenkins-maven-nightly"
> + depends="clean,remove-maven-artifacts,generate-maven-artifacts,run-
> mav
> + en-build,validate-maven-dependencies"/>
> 
>    <target name="jenkins-clover" depends="run-clover"/>  </project>



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to