Include files in target

[Philip Grove]

Although it should not be a problem, I want to exclude everything except *.java files from my Ant build targets. But when I test using ant -v I can see that every single file in the directory tree is being tested and all except *.java files are being skipped as Ant don't know how to handle them.

The problem is probably simple to solve but given my very short experience with Ant (less than two days) I haven't been able to figure it out myself, despite a massive amount of searching.

As you can see from the build.xml file, my project is split across three packages which depend on each other.

<?xml version="1.0"?>
<project name="DataServer" default="server" basedir=".">
	<property name="serverdir" value="dk/lokus/server"/>
	<property name="collectdir" value="dk/lokus/server/collect"/>
	<property name="datamodeldir" value="dk/lokus/server/collect/datamodel"/>

	<target name="server" depends="collect,datamodel">
		<fileset dir="${serverdir}">
			<include name="**/*.java"/>
		</fileset>
		<javac srcdir="${serverdir}" destdir="${serverdir}"/>
	</target>

	<target name="collect" depends="datamodel">
		<fileset dir="${collectdir}">
			<include name="**/*.java"/>
		</fileset>
		<javac srcdir="${collectdir}" destdir="${collectdir}"/>
	</target>

	<target name="datamodel">
		<fileset dir="${datamodeldir}">
			<include name="**/*.java"/>
		</fileset>
		<javac srcdir="${datamodeldir}" destdir="${datamodeldir}"/>
	</target>
</project>

[Tim Holloway]

The way it looks to me is that you think "fileset" is some sort of magic definition that the javac task is expected to intuitively pick up and use. Ant doesn't intuitively pick up anything and each element is expected to be self-contained. If you want Ant to use it, you have to explicitly tell Ant to use it.

fileset is a qualifier applicable to some (but not all Ant task types). To make it work, it has to be an embedded element of the task that's filtering files. Or, alternatively, it can be a named definition that's done external to the list of targets and then referenced by name by those tasks that wish to apply the filtering rules it defines.

[Philip Grove]

Actually what I think in relation to the <fileset> element is very limited as the information I have found by searching and reading documentation is conflicting. But I don't remembering trying it as an embedded element of the tasks so I will look into that when my code actually compiles again.

Thanks for the input

[David Newton]

I don't think the javac task manual page is terribly conflicting; here's one of their examples:

  <javac srcdir="${src}"
         destdir="${build}"
         classpath="xyz.jar"
         debug="on"
         source="1.4"
  />

Note the lack of a fileset, because it's simply not necessary. Here's another option:

  <javac sourcepath="" srcdir="${src}"
         destdir="${build}" >
    <include name="**/*.java"/>
    <exclude name="**/Example.java"/>
  </javac>

Still no fileset, because it's not necessary.

[Philip Grove]

It is necessary if you want to avoid getting other files looked at, but that is harmless. There is another reason that there is no fileset, it is not allowed in the javac task. Your second example almost gives away the solution, the parameters include and exclude.

But you are right that the manual page is pretty clear, how I missed it remains a mystery to me. That could have saved a lot of time for everybody.

[David Newton]

The files are going to be looked at no matter what--*something* will decide whether or not it should be compiled.