Stefan, Will setFile( File ), be able to handle multiple files? How would ProjectHelper know if the attribute contained a String or a File?
Why not just stay with strings and let Task designers decide what to do with property strings at set time? It seems like this is the most flexible design, but it necessitates some common functions, one of which is already available in Project.resolveFile(). Another function that there is already a need for is a parseMultiple() function to resolve multiple string inputs. Tim O'Brien [EMAIL PROTECTED] At 12:51 PM 6/28/00 +0200, Stefan Bodewig wrote: > >>>>> "TO" == Tim O'Brien <[EMAIL PROTECTED]> writes: > > TO> Also, I see that some tasks are using Project.resolveFile() for > TO> file resolution and some are not. I take it that the standard is > TO> to use resolveFile(). > >We are going to have attributes that are not restricted to Strings any >longer - not that far in the future I hope. > >As soon as this has been done, let's go out and replace all >setFile(String) methods with setFile(File) and let ProjectHelper >invoke this using Project.resolveFile. That's the most consistent we >could get. > >Stefan
