On Thursday 09 October 2003 15:43, Dominique Devienne wrote:
> > -----Original Message-----
> > From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
> >
> > On Thu, 9 Oct 2003, John-Mason Shackelford
> >
> > <[EMAIL PROTECTED]> wrote:
> > > Then computeBuildPath would operate as follows:
> >
> > As Dominique's version needs a separate file with extra information
> > as well, I'd say it is fine for the algorithm (I prefer to keep it
> > pluggable) to pick up additional files.
>
> Actually, the build path resolver's contract is to "load" the
> Dependency graph and resolve it, handing the result out, but that
> doesn't mean that graph cannot be specified inside the build file itself.
>
> It was impractical before Ant 1.6, because pluggeable components could
> only be configured using <param>, but no more thanks to Peter.
>
> If you have:
>
> public class BuildPath extends Path {
> public void addType(BuildPathResolver resolver) {...}
Nit picking...
This should be "public void add(BuildPathResolver resolver) {...}"
Peter
> }
>
> You can now do something like the following:
>
> <project ...>
> <typedef name="antdepsresolver"
> classname="com.wunderbar.AntDepsResolver" ... />
> <buildpath id="dependencies>
> <antdepsresolver>
> <fileset dir="${dependencies.dir}" includes="*/build.xml" />
> <depend project="util" />
> <depend project="commons" />
> ...
> </antdepsresolver>
> </buildpath>
> </project>
>
> So no need for external files, and everything done in Ant. --DD
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
