[jboss-jira] [JBoss JIRA] Commented: (JBAS-7675) Revert to javassist 3.10

Brian Stansberry (JIRA) jira-events at lists.jboss.org
Mon Feb 1 15:07:19 EST 2010


    [ https://jira.jboss.org/jira/browse/JBAS-7675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12509651#action_12509651 ] 

Brian Stansberry commented on JBAS-7675:
----------------------------------------

Further research by Andrew showed the issue he was seeing was not introduced in 3.11, so there's no point in reverting. It will be fixed in javassist 3.12. I'll keep this open until next week just as a reminder to myself to check on javassist 3.12. But my 99% expectation is M2 will stick with the current 3.11.

> Revert to javassist 3.10
> ------------------------
>
>                 Key: JBAS-7675
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7675
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: AOP
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>            Priority: Critical
>             Fix For: JBossAS-6.0.0.M2
>
>
> Andrew Dinn is reporting some problems with javassist 3.11 (see http://lists.jboss.org/pipermail/jboss-development/2010-January/015624.html) and Kabir indicates that AS shouldn't need to move beyond 3.10. So, look at reverting back.
> I'll do this the first week of Feb after the smoke is cleared from the component upgrades coming in right now for the M2 cutoff.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list