Re: handling external resources

[Erik Hatcher]

I don't know of any tasks that set hidden datatypes.  So in that respect 
you'd be going off the beaten path.  A "well behaved" datatype would be 
something that a user would specify explicitly:

        <myDatatype id="a.datatype" someAttribute="whatever"/>
And then later refer to it by refid="a.datatype".
        Erik
Shackelford, John-Mason wrote:
Erik,

I think you'll have to use your best judgement on how to do this - 
but you could still set a project-scoped datatype from within your 
task that later tasks could see, and the user would never see an 
actual datatype declaration.

Thanks, that helps. I really don't want to be wacky, so understanding that
this is a legitimate use of a project-scoped datatype will help me move
ahead with a little more confidence. I am grateful to have ant and want very
much to make a meaningful contribution, but if my code is too far afield it
won't be of use to anyone.
John-Mason Shackelford
Software Developer
NCS Pearson - Measurement Services
2510 North Dodge St.
Iowa City, IA 52245
319-354-9200x6214
[EMAIL PROTECTED]
**************************************************************************** 
This email may contain confidential material. 
If you were not an intended recipient, 
Please notify the sender and delete all copies. 
We may monitor email to and from our network. 
****************************************************************************

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>