On Fri, 05 Aug 2011 13:51:57 -0300, Howard Lewis Ship
wrote:
Some of the minor things that were deprecated in 5.2 were removed in
5.3; if there's enough outcry, they can be restored (such as
@IncludeJavaScriptLibrary, etc.).
For each major version change we can create a backward-compatibili
It does make sense that RenderSupport stay in until 5.4. For really
important things, having two full releases for people to upgrade makes
sense before the class is removed. RenderSupport was deprecated in
5.2, so 5.4 makes sense.
Some of the minor things that were deprecated in 5.2 were removed
Hi Howard
It is being used in tapestry-upload. I had submitted a patch for that
sometime back
https://issues.apache.org/jira/browse/TAP5-1564
regards
Taha
On Fri, Aug 5, 2011 at 5:54 PM, Howard Lewis Ship wrote:
> Slight correction: RenderSupport is still available but will be
> removed in 5.
Slight correction: RenderSupport is still available but will be
removed in 5.4. While you are rummaging through your code to fix your
imports, update your use of RenderSupport to JavaScriptSupport.
On Fri, Aug 5, 2011 at 5:19 AM, Howard Lewis Ship wrote:
> You know you're gonna wanna do it ... up
You know you're gonna wanna do it ... upgrade to 5.3, when it's ready.
Tapestry 5.3 is faster, learner, and has new features and new
components, including the unified alerts subsystem, the Tree and
Kaptcha components, JavaScript minification, JPA integration, and
more.
A couple of my clients have
