tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-853) Move away from Javassist
Date Mon, 02 May 2011 23:52:03 GMT

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

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

Integrated in tapestry-trunk-freestyle #334 (See [https://builds.apache.org/hudson/job/tapestry-trunk-freestyle/334/])
    TAP5-853: Create an implementation of PlasticProxyFactory.getMethodLocation() and getConstructorLocation()
based on ASM Tree API (not ClassFactory)


> 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

Mime
View raw message