[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

[Ben Speakmon (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_26772 ] 

Ben Speakmon commented on HHH-2222:
-----------------------------------

Alistair, I'm doing something very similar to you -- I'm integrating a source build of hibernate, and I'm also using that version of hibernate in a spring source build.

Spring uses the cglib-nodep artifact, which takes asm 1.5.3 and repackages it inside cglib as net.sf.cglib.asm. Spring itself uses ASM 2.2.3 in a couple of places and uses it unchanged from their stock distribution. This private version of asm is used only by cglib and amounts to a private static dependency.

I've started work on a hibernate patch that uses the asm inside the cglib package, but I haven't finished it yet (probably be done early of next week). Since Hibernate uses 1.5.3 ASM and cglib uses 1.5.3 ASM, it should work with only source changes.

> 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
>          Issue Type: Improvement
>    Affects Versions: 3.2.0.ga
>         Environment: Hibernate 3.2.0ga
>            Reporter: Greg McGregor
>   Original Estimate: 0 minutes
>  Remaining Estimate: 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