lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitry Serebrennikov <>
Subject Re: build.xml still requires anakia
Date Mon, 15 Oct 2001 17:47:41 GMT
Yes. It fails every time. The problem is in this statement:
  <path id="anakia.classpath">
    <fileset dir="${jakarta.site2.home}/lib">
      <include name="*.jar" />
which is included at the "project" level. I imagine there must be a way 
to include it at a "target" level instead, but I didn't investigate. 
Commenting it out works fine, but it would be better, if we didn't have 
to modify this file for different compilation scenarios.

Doug Cutting wrote:

>>From: Dmitry Serebrennikov []
>>The latest build.xml works fine with Ant and without the batch files, 
>>but it has a classpath statement that fails if anakia is not 
>If I remove anakia, then it only fails for me when I try to build the "docs"
>target, which is the target that requires anakia.  That is the desired
>behavior.  Are you seeing behavior different than this?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message