Well, I'm certainly open to that... I didn't view it as anything but adding to the existing library so my first thought was not a new subproject. As I mentioned in the post, it doesn't alter any existing code written against the taglib as it exists today, and in my mind that makes it not a new subproject.

If everyone agreed it should be though, I wouldn't argue. But at least at this point, I don't see it that way, I think it really is just an expansion on the existing project. In fact, since my thinking was that this should be a drop-in replacement for the existing taglib, that says to me it shouldn't be a new subproject (unless there is some reason that goal is not a good idea?).

--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com


Ted Husted wrote:
Frank,

I believe this initiative would be framed as a separate subproject,
would it not?

Which is to say, the original taglib product would remain the same.

This product would extend and build on the original taglibs, to create
a separate distribution, yes?

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




.




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to