Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tapestry.apache.org
Date: Tue, 3 May 2011 22:21:03 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: commits@tapestry.apache.org
Message-ID: 
 <2117473622.19967.1304461263677.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (TAP5-853) Move away from Javassist
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/TAP5-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028472#comment-13028472 ] 

Hudson commented on TAP5-853:
-----------------------------

Integrated in tapestry-trunk-freestyle #335 (See [https://builds.apache.org/hudson/job/tapestry-trunk-freestyle/335/])
    TAP5-853: Re-implement debugging-mode field write-behind
TAP5-853: Add support for field write-behind (useful for debugging) when connecting a field to a FieldConduit


> Move away from Javassist
> ------------------------
>
>                 Key: TAP5-853
>                 URL: https://issues.apache.org/jira/browse/TAP5-853
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.3.0
>
>
> A long-term, multi-release strategy to replace ClassFactory/ClassGen and ClassTransformation methods with equivalents that are not tied to Javassist.
> Over a couple of releases, the methods could be introduced (still implemented on top of Javassist), and the Javassist-centric methods deprecated, then eventually disabled (NotImplementedException) or even removed.
> Rationale: Javassist is unprofessionally and fitfully maintained; many users have problems under Java6 due to Javassist.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira