I agree with Stefan on this. In my case, I have multiple compilation stages as part of the build. For example, we need to compile the our own code generator, then generte code, then compile the generated code, etc. And then we have different rules to compile just the escentials or the whole thing.
However, the depends task would need to take a global view at the sources since there are interdependencies between all these stages. Having the two toghether would make matters just worst,because I will have more repetitive depends analysis instaead of just one big swoop. Jose Alberto > -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 26, 2001 7:59 AM > To: [EMAIL PROTECTED] > Subject: Re: [VOTE] The late stuff > > > > * Integration of the depends task and javac tasks > > Why, what's wrong with invoking two tasks in sequence? > > I usually have a pattern like this in my build files > > <target name="depend" if="dependprop"> > <depend srcdir="${sourcedir}" destdir="${classes}" > cache="dep.cache"> > <patternset refid="all.sources" /> > </depend> > </target> > > <target name="compile" depends="depend"> > <javac srcdir="${sourcedir}" destdir="${classes}" > encoding="iso-8859-1"> > <patternset refid="all.sources" /> > </javac> > </target> > > which makes it possible to compile without the depend task and only > run it, if I know I'm going to need it (by using ant -Ddependprop=1). > > You only need to run <depend> if you've made changes to the interface, > not the implementation of something, so running it all the time would > be a pain. > > I don't need to mention, that recompiling everything using jikes would > be faster than doing an extensive dependency check, as Pete will do > that 8-) > > > * recursive property resolution( ie resolving ${dist.${name}.dir} ) > > Could I have a use case for this please - something real > worldish, that > you cannot (conveniently) solve be something other than that? > > Stefan >
