A path definition, that contains a fileset might depend on the time, it is
evaluated:
<path id="some.path">
<pathelement path="${build.classpath}/" />
<fileset dir="${build}/lib">
<include name="*.jar" />
</fileset>
</path>
One of four things might happen:
1. {build} has not been mkdir-ed -> build fails
2. {build}/lib exists, but is still empty
3. {build}/lib contains the contents from a previous ant-call
4. if the target, that generates {build}/lib has executed already,
the path will contain the current set of jars
This makes path definitions (maybe other datatype usage, too) less
helpful, they could be.
possible solution:
-> evaluate the path definition on demand - probably more than once a
build
rationale:
-> a target depends on a path, the same way as targets depend on other
targets
Discussion?
Holger
