Jacek, I don't have a clear overview on that point. But it seems to me important to keep OpenEJB - JPA vendor independent (OpenJPA, Hibernate, TopLink ...).
Some months ago, David did changes on that topic http://www.nabble.com/Heads-up----shading-asm-deps-td18900815.html#a18900815 http://www.nabble.com/Heads-up----shading-asm-deps-td18900815.html#a18900815 . As far as I can remember, it was to get rid of ASM dependency (using the well known maven shade plugin). My understanding is that if you go back to org.objectweb package you will face hibernate issues because of ASM versions. Is that true ? Jean-Louis > and use it instead of org.objectweb. It was once with asm-finder, but > it got removed. I wonder why? Shouldn't it be a regular OpenEJB module > with a proper dependency mg,t so when we want to upgrade XBean it will > boil down to updating pom (in its easiest case)? I'm ready to > implement it unless it gets banned. I'll commit necessary changes unless it gets voted against. Anyone? Jacek -- Jacek Laskowski Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl -- View this message in context: http://www.nabble.com/asm-repackaging---asm-finder-%2B-our-asm-package-in-use-highly-needed-tp23575152p23611210.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
