|Summary:||say which jar/class is wrong when throwing UnsupportedClassVersionError|
|Product:||Tomcat 6||Reporter:||Ralf Hauser <hauser>|
|Component:||Catalina||Assignee:||Tomcat Developers Mailing List <dev>|
Description Ralf Hauser 2008-03-19 08:25:39 UTC
Comment 1 Ralf Hauser 2008-03-24 01:15:41 UTC
Created attachment 21704 [details] Lsjar.java this is an approach to determine whether your jar files are the culprits so, if there is java5 the requirement, you shouldn't see a major of 50 java -jar lsjar.jar -dir -jvmVersion /usr/share/tomcat/shared/lib/ | grep -v 48 | grep -v 46 | grep -v 49 | grep -v 47 | grep -v 45 -- in my case, they aren't :(
Comment 2 Mark Thomas 2008-03-24 08:59:13 UTC
I have patched trunk and proposed it for inclusion in 6.0.x
Comment 3 Mark Thomas 2008-04-05 11:32:19 UTC
This has been fixed in 6.0.x and will be in the 6.0.17 onwards.
Comment 4 Arnaud Jotterand 2008-04-15 06:47:29 UTC
Created attachment 21822 [details] Lsjar2.java Some class files of a jar may not have been compiled with the same version of Java than the others. It therefore may be useful to check the version of each class file contained in a jar.
Comment 5 Arnaud Jotterand 2008-04-15 06:49:27 UTC
Comment on attachment 21822 [details] Lsjar2.java Added an -all option to Lsjar.java that allow to check every class file in a jar.