On Mon, 07 Feb 2011 10:12:03 -0200, Howard Lewis Ship <[email protected]>
wrote:
Ok, I'll create sub-task issues for these cases.
Another +1 to that.
In a case-by-case basis, I think it would be interesenting to provide some
separate JARs containing some deprecated feature. I'd call them
backward-compatibility packages. This way, people with code written using
something that was deprecated can still run its code without changes and
we can say that Tapestry 5 is backward-compatible. ;)
One example is of the old URL rewriting code. The LinkTransformer API
doesn't handle 100% of the scenarios the old one does.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
