James Duncan Davidson <[EMAIL PROTECTED]> wrote: > On 12/14/00 9:18 AM, "Stefan Bodewig" <[EMAIL PROTECTED]> wrote:
>>> This is also where I'm thinking that the regexp functionality >>> should go (based on jakarta-regexp). >> >> What regexp functionality? Sorry, I can't follow you here. > > To deal with regexp patterns in attributes. When a task allows > regexp info in an attribute/element, it should just be able to ask > Ant to resolve it or ask if 2 things match. Never thought regexp functionality would be that common in Ant tasks that it should be put into the base class - no problem with that, it just hasn't popped up before at all. >> One last thing. I don't think Project should take care of >> properties at all. I'm still in favor of unifying properties with >> data types and think they should be handled via some external >> store. > > Properties belong to a project. Whether they are strings or more > sophisticated Data types is are different. > Sure properties belong to the project, but this doesn't mean project needs to manage them itself. Just like TaskManager is there to manage name -> implementation mappings for tasks a PropertyManager/Store could (and should IMHO) take care of the data side of build files. Stefan
