Ah, let's be careful here... You're idea is a good one, and we should hang on to it...
But, it is NOT a requirement, it's a DESIGN proposal. Right now we are trying to collect the requirements of WHAT ant should do, then in the next phase we figure out HOW to do it all. Your idea looks good, but I think what got us into the raging war last time was getting the requirements definition and various designs so inter-twined, no one could agree... > Stephane Bailliez wrote: > > What about simply using the manifest as the task properties ? > > ant.jar > ant-task: org.apache.tools.ant.taskdefs.Property > ant-task: org.apache.tools.ant.taskdefs.Move > ... > > optional.jar > ant-task: org.apache.tools.ant.taskdefs.optional.javacc.JavaCC > ant-task: org.apache.tools.ant.taskdefs.optional.javacc.JJTree > ... > > mytasks.jar: > ant-task: com.mycompany.mytools.ant.mytasks.mytask > ... > > -- > St�phane Bailliez > Software Engineer, Paris - France > iMediation - http://www.imediation.com > Disclaimer: All the opinions expressed above are mine and not those from my > company. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
