Lots of things beyond just this are likely going to break or act in undefined ways when you have the entire uPortal project on the classpath twice (what having -classes.jar and the /target/classes dir results in).
-Eric On 1/15/13 11:12 AM, Paul Gazda wrote:
In uP 4.0.8, I have a dependency jar defined in the uportal-war pom.xml that uses hibernate. It is part of an important custom student center portlet that we use. When I include it and run deploy-war, I get many test failures with this error:Caused by: java.lang.IllegalStateException: Conflicting persistence unit definitions for name 'PortalDb': file:/C:/Users/pag/.m2/repository/org/jasig/portal/uportal-war/4.0.8/uportal-war-4.0.8-classes.jar, file:/C:/JavaClasses/uportal.git/uportal-war/target/classesThis seems to be related to a bug in Spring reported here: http://www.mulesoft.org/jira/browse/MULE-6241 <http://www.mulesoft.org/jira/browse/MULE-6241>When I change the spring version to 3.2.0, the test errors go away, but uportal does not start because of spring related errors.There seems to be a way of overriding a spring 3.1.3 method to work around the problem, but not being very familiar with spring, I find it very confusing as to how an internal spring method is overridden.Unless there is something fairly straightforward that will fix this problem, I'm wondering if it would be possible to upgrade to spring 3.2.0 in the next release of uP4.Thanks. Paul Gazda -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
smime.p7s
Description: S/MIME Cryptographic Signature
