rsanders
2014-05-23 20:14:32 UTC
Hello everyone,
Got a question that is either a fundamental problem or naive question
(possibly both). First - I'm *not* a java/grails/groovy developer, but a
C/C++/Python guy who has inherited a Grails project. Migrated it from
Grails 1.3.7 to Grails 2.2.2 and now Grails 2.3.7 and it still works, so
I've learned a little bit I went. App is deployed under Tomcat 6.
Our app is basically using hsqldb (for legacy), with the shiro 1.1.4,
jquery 1.8.3, and webflow plugins, and Ivy as the dependency manager. When
I look at the jar files that are included in the resulting war file I see
two different hibernate-jpa files, and two different javassist files.
Specifically hibernate-jpa-2.0-1.0.1-Final.jar,
hibernate-jpa-2.1-1.0.0.Final.jar, javassist-3.7.ga.jar, and
javassist3.17.1-ga.jar. The javassist files seem to come from different
groups (org.javassist and jboss.javassist respectively). If I change to
aether/maven the hibernate-jpa-2.0* jar isn't referrenced or packaged.
A quick look at the similar jars seems to show "mostly" the same class
files . So if similar classes are being presented, is Tomcat quietly
dropping one of the duplicates, or is the classloader managing to keep
straight who wants which version?
-Rob
--
View this message in context: http://grails.1312388.n4.nabble.com/duplicate-jar-files-how-to-resolve-tp4657014.html
Sent from the Grails - user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Got a question that is either a fundamental problem or naive question
(possibly both). First - I'm *not* a java/grails/groovy developer, but a
C/C++/Python guy who has inherited a Grails project. Migrated it from
Grails 1.3.7 to Grails 2.2.2 and now Grails 2.3.7 and it still works, so
I've learned a little bit I went. App is deployed under Tomcat 6.
Our app is basically using hsqldb (for legacy), with the shiro 1.1.4,
jquery 1.8.3, and webflow plugins, and Ivy as the dependency manager. When
I look at the jar files that are included in the resulting war file I see
two different hibernate-jpa files, and two different javassist files.
Specifically hibernate-jpa-2.0-1.0.1-Final.jar,
hibernate-jpa-2.1-1.0.0.Final.jar, javassist-3.7.ga.jar, and
javassist3.17.1-ga.jar. The javassist files seem to come from different
groups (org.javassist and jboss.javassist respectively). If I change to
aether/maven the hibernate-jpa-2.0* jar isn't referrenced or packaged.
A quick look at the similar jars seems to show "mostly" the same class
files . So if similar classes are being presented, is Tomcat quietly
dropping one of the duplicates, or is the classloader managing to keep
straight who wants which version?
-Rob
--
View this message in context: http://grails.1312388.n4.nabble.com/duplicate-jar-files-how-to-resolve-tp4657014.html
Sent from the Grails - user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email