RE: [Ant-contrib-developers] Recent changes and development direc tion

[Dominique D. <DDe...@lg...>]

> From: Inger, Matthew [mailto:Inger@Synygy.com]
> 
> Why not a service locator pattern for compiler adapters.
> Why should the user need to put in the entire classname?
> They should merely drop in the jar, and use a reasonable name.
> 
> At startup, cpptasks would then query for the available compiler
> adapters using some discovery mechanism, which would lead them to
> the service locator for that particular adapeter.
> 
> On May 13, 2004, at 11:48 AM, Dominique Devienne wrote:
> > 7) Ability to define new compiler/linker adapters without having
> >    to recompile CppTasks to plug in the enums for them.

Because Ant doesn't do it, for the good reason (IMHO) that it wants
things to be in the open / explicit. This is why you need to explicitly
taskdef/typedef your tasks/types. Even with the new automagic AntLib
stuff, you need to specify the AntLib's URI explicitly.

CppTasks being an extension to Ant, I'd rather it sticks to Ant way
of discovering extensions. --DD