Hi,
I am in need of a mechanism to be able to define user defined Tag->Class mappings *before* the
names of the default types and tasks are mapped.
I have attached a patch herewith. Comments?
Cheers, Magesh
Magesh,
I think the reliance on system properties may be a problem. It will not be evident from a build file what tasks definitions are in use and therefore build files become a bit more mysterious to users. Taking a build file from one environment to another is not guaranteed to work and there is no hint in the build file itself about what definitions/libraries are missing.
Today, taskdefs are either the standard ant ones or those explicitly defined in the buildfile. Even with <antlib> you need to somehow specify which libraries are in use even if you can "install" them simply by dropping into some known location.
Conor
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
