we have the same nightly build failures over and over whenever anybody upgrades lucene -- from now on, let's fail fast if lucene_version doesn't match the lucene jars in lib so whoever does the jar upgrade gets an error before they even waste time compiling Solr

git-svn-id: https://svn.apache.org/repos/asf/lucene/solr/trunk@817089 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Chris M. Hostetter 2009-09-20 19:48:37 +00:00
parent e5cb88d922
commit 60f17a9c59
1 changed files with 14 additions and 0 deletions

View File

@ -84,6 +84,20 @@
<target name="init-forrest-entities"> <target name="init-forrest-entities">
<!-- no description, don't advertise --> <!-- no description, don't advertise -->
<available file="lib/lucene-core-${lucene_version}.jar"
property="lucene-version-ok-m2deploy-wont-fail" />
<fail unless="lucene-version-ok-m2deploy-wont-fail">
lib/lucene-core-${lucene_version}.jar Missing
lib/lucene-core-${lucene_version}.jar does not exist.
This will cause problems with m2-deploy later, so fail fast now.
Probably cause: lucene jars were upgraded w/o modifying the
'lucene_version' property in common-build.xml
</fail>
<mkdir dir="${dest}" /> <mkdir dir="${dest}" />
<!-- A folder containing the expanded war file --> <!-- A folder containing the expanded war file -->