lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Hostetter <>
Subject javadoc classpath cleanup?
Date Wed, 09 May 2007 17:54:01 GMT

i just commited what i thought was a minor fix to teh build.xml to update
the contrib list in the javadoc task .. only afterwards did i realize this
exposed some new warnings/bugs in the contrib/db javadocs, which seem to
be because the jars it dpeends on arent' being included in the

is there any particular reason why javadoc.classpath is defined by
enumarating the list of jars, instead of using something like...

  <!-- Javadoc classpath -->
  <path id="javadoc.classpath">
    <path refid="classpath"/>
    <pathelement location="${ant.home}/lib/ant.jar"/>

    <!-- NOTE: gdata jars only used with jdk 5 but include them even for lower jdk -->
    <fileset dir="contrib">
        <include name="**/*.jar"/>

(i know we have to enumarate all of the packagesets and groups in the
javadoc task, but there doesn't seem to be any good reason to enumerate
all the lib jars when defining the classpath)


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message