----- Original Message ----- From: "stephan beal" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, March 23, 2002 5:01 AM Subject: Cvs <commandline> implementation question...
> hey, all... > > i'm starting on the nested <commandline> implementation for AbstractCvsTask, > and i've found that i'd like to implement it using a private ExecTask, and > simply act as a proxy to that object (it's too much code to duplicate, IMO). > However, many of the functions i'd need from ExecTask are protected. So, that > leaves me with two options: > > a) "open up" ExecTask - make more methods public. > b) subclass AbstractCvsTask from ExecTask. > > Which would be the prefered approach for the project? It doesn't make much > difference to me, either way. i can see some sense in subclassing ExecTask, > anyway, but if that offends anyone too greatly i won't do it. if you look at the optional/dotnet classes, you can see that I wrote a couple of base classes for all the tasks to use... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
