Ah! Yes, both of these were in the war file: WEB-INF/lib/aspectjweaver-1.6.10.jar WEB-INF/lib/aspectjweaver-1.8.5.jar
Mahalo for your insight. When I deleted aspectjweaver-1.6.10.jar from the war file, CAS deployed without error. I suppose the quesion now is, how do you prevent Maven from including the old version? Aloha, -baron On Wed, Mar 11, 2015 at 10:48:56PM -0500, Richard Frovarp wrote: >Check the lib directory. Are you ending up with two versions of that >library? > >I'm interested in what you find out / do. We have 3.4.12 against Tomcat 7 >that we need to take from Java 7 to Java 8 here shortly. CAS is the one >thing I haven't tested yet. > >On Wed, Mar 11, 2015 at 10:19 PM, Baron Fujimoto <[email protected]> wrote: > >> I'm in the process of updating the our CAS 3 software infrastructure. We >> were running CAS 3.4.11, with Java 1.6.x under Tomcat 6.0.x. I'd like to >> get these software versions to their current releases. My plan was first >> to update Java (1.8.x) and Tomcat (8.0.x), and when I was satisfied that >> was working as expected, update CAS to 3.5.3 (updating to CAS 4 is a >> project for another day). >> >> After updating Java and Tomcat however, I've run into problems redeploying >> CAS. Maven appears to build the war file ok, but when I launch the webapp, >> I encounter the following exceptions: >> >> INFO: Deploying web application archive /home/cas/tomcat/webapps/cas.war >> org.aspectj.apache.bcel.classfile.ClassFormatException: Invalid byte tag >> in constant pool: 15 >> at >> org.aspectj.apache.bcel.classfile.Constant.readConstant(Constant.java:133) >> at >> org.aspectj.apache.bcel.classfile.ConstantPool.<init>(ConstantPool.java:45) >> at >> org.aspectj.apache.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:186) >> at >> org.aspectj.apache.bcel.classfile.ClassParser.parse(ClassParser.java:131) >> at >> org.aspectj.apache.bcel.util.NonCachingClassLoaderRepository.loadJavaClass(NonCachingClassLoaderRepository.java:262) >> at >> org.aspectj.apache.bcel.util.NonCachingClassLoaderRepository.loadClass(NonCachingClassLoaderRepository.java:242) >> at >> org.aspectj.apache.bcel.util.NonCachingClassLoaderRepository.loadClass(NonCachingClassLoaderRepository.java:249) >> at >> org.aspectj.weaver.reflect.Java15AnnotationFinder.getAnnotations(Java15AnnotationFinder.java:202) >> at >> org.aspectj.weaver.reflect.ReflectionBasedResolvedMemberImpl.unpackAnnotations(ReflectionBasedResolvedMemberImpl.java:211) >> at >> org.aspectj.weaver.reflect.ReflectionBasedResolvedMemberImpl.hasAnnotation(ReflectionBasedResolvedMemberImpl.java:163) >> at >> org.aspectj.weaver.patterns.ExactAnnotationTypePattern.matches(ExactAnnotationTypePattern.java:109) >> at >> org.aspectj.weaver.patterns.ExactAnnotationTypePattern.matches(ExactAnnotationTypePattern.java:96) >> at >> org.aspectj.weaver.patterns.AnnotationPointcut.matchInternal(AnnotationPointcut.java:156) >> [...] >> >> A little cursory Googling suggested that with Java 8, you need AspectJ >> 1.8, so I added the following to pom.xml: >> >> <dependency> >> <groupId>org.aspectj</groupId> >> <artifactId>aspectjweaver</artifactId> >> <version>1.8.5</version> >> </dependency> >> >> After I rebuild and deploy, I still see the same exceptions though. Am I >> on the right >> path at all with this? Any suggestions would be appreicated. >> >> Aloha, >> -baron >> -- >> Baron Fujimoto <[email protected]> :: UH Information Technology Services >> minutas cantorum, minutas balorum, minutas carboratum desendus pantorum >> >> -- >> 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/cas-user -- 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/cas-user
