[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2222) SpringFramework 2.0 uses ASM.JAR versions 2.2.2. This is incompatible with Hibernate 3.2 as it uses and "unknown" previous version of ASM.JAR

[Greg McGregor (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2222?page=comments#action_25216 ] 

Greg McGregor commented on HHH-2222:
------------------------------------

Thanks for the version feedback.  

I was taking 3.2.0.ga and replacing the hibernate3.jar that Spring provided to bring the latest bug fixes up to date when I noticed the problem.  Since the JAR that ships from Spring works fine (previous RC to 3.2) and your stuff works fine independently, I should just stick with the Spring shipped release.  The ASM versions each uses are much different so I'm scratching my head.  However, I would like to use 3.2.0ga so if I find something useful, I'll comment back.

> SpringFramework 2.0 uses ASM.JAR versions 2.2.2.  This is incompatible with Hibernate 3.2 as it uses and "unknown" previous version of ASM.JAR
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: HHH-2222
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2222
>      Project: Hibernate3
>         Type: Improvement

>     Versions: 3.2.0.ga
>  Environment: Hibernate 3.2.0ga
>     Reporter: Greg McGregor

>
> Original Estimate: 0 minutes
>         Remaining: 0 minutes
>
> SpringFramework 2.0 uses ASM.JAR from ObjectWeb version 2.2.2.  However, Hibernate 3.2.0ga utilizes an "unknown" previous version of the ASM.JAR.  The issue is that the method signatures and classes have changed between the two versions.  Therefore, Hibernate 3.2.0ga won't run with the new ASM.JAR and Spring 2.0 won't run with the previous ASM.JAR.  Mushing the two JARs together in an attempt to get something going results in a NoSuchMethodError (which would make sense).
> Although this isn't a direct Hibernate3 bug, it does preclude stable use with Spring 2.0/

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