Jesse, but this is not a Tacos issue. I mean, even if Tacos didn't have
a duplicated Form component, Tapestry should take care on its own of not
breaking the API on small bugfix releases.
Rather, the issue is about Tapestry not having a deprecated or
overloaded component that fits the old interface.
But I know nobody wants to hit you in the head for doing this. You and
Brian have been doing a great job, actually. Rather, what I suggest is
to fix the Tapestry interface and do a small release. The question is:
is it worth it?
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Jesse Kuhnert wrote:
I guess that's fair. I think I must have discounted tacos because I'm on
that project as well, and I know that the only people who would be affected
by such a change would be people who completely duplicated the Form
component (as I did). Sorry for not releasing the new tacos with tap 4.0.1.
Will try to be sure this doesn't happen in the future.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
