This reminds me of a project we have in-house. First, we created interfaces for all the important classes. Then, in the XML, we have an optional attribute where the classname may be specified.
This allows the developers to extend our classes or completely replace them. So here you'd have <target classname="mytarget"> ----- Original Message ----- From: Steve Loughran <[EMAIL PROTECTED]> To: Ant Users List <[EMAIL PROTECTED]> Sent: Thursday, December 20, 2001 12:02 PM Subject: Re: Proper use of <uptodate> (a little off-topic) > > ----- Original Message ----- > From: "DONNIE HALE" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, December 20, 2001 11:18 AM > Subject: Re: Proper use of <uptodate> (a little off-topic) > > > Thanks for the info. I understand the point, though I tend to agree with > you - just move the line in the sand past equality but short of all the > other things he's worried about. :) > > Since I have your attention, 2 questions (1 related): > > >1) I know that tasks are extensible. How about <target>s? So someone could > post a contributed, >enhanced <target> without changing the core. > > I dont think anyone has tried. anything which can be a direct child of > <project> is special; they are hard coded into some file or other, then > there is the whole graph creation and traversal code which probably looks > for target only...that might need to be tweaked to use instanceof checks or > something., > > -steve > > > -- > 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]>
