[SAK-17578] Compiling with Java 1.6 breaks tools in Sakai Created: 14-Dec-2009  Updated: 22-Jun-2016  Resolved: 02-Nov-2010

Status: CLOSED
Project: Sakai
Component/s: Other
Affects Version/s: 2.7.0
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Alan Berg Assignee: Core Team
Resolution: Won't Fix Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

qa1-nl, qa1-za

Issue Links:
duplicates SAK-15874 Switch to Java 1.6 (Java 1.5 EOL 30-O... CLOSED
incorporates SAK-36324 Samigo broken by compiling with Java 1.6 CLOSED
incorporates SAK-16745 Java 1.6 change/fix in classloader.lo... CLOSED
is related to SAK-19046 Add sakai-start-java6 startup scripts... CLOSED
SAK-17579 OSP fails if compiled on Java 1.6 Sub-task CLOSED OSP Jira Team  
SAK-17580 Blogger fails when compiled on Java 1.6 Sub-task CLOSED Core Team  
CLE Team Issue:


A number of tools are broken in a similar way to: http://jira.sakaiproject.org/browse/SAK-16745

2009-07-23 14:48:57,191 INFO main org.apache.catalina.startup.HostConfig - Deploying web application archive sakai-chat-tool.war
java.lang.ClassNotFoundException: [Ljava.lang.String;
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1359)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1205)

This happens due to compiling with Java 1.6. The short term work around is to add the following option in the tomcat startup script.

Code needs to be updated to avoid this.



Comment by Stephen Marquard [ 14-Dec-2009 ]

I think the above are all JSF dependencies (certain T&Q and Chat). Given the potential impact of upgrading JSF versions (especially for T&Q), I think this is inappropriate for 2.7 and should target 2.8.

Comment by Anthony Whyte [ 02-Mar-2010 ]

Addressing this issue will be deferred to either 2.8 or a later 2.7 maintenance release. The current workaround is to add the following environment parameter to JAVA_OPTS.


Comment by Anthony Whyte [ 02-Mar-2010 ]

Lowering the status to critcal.

Comment by Beth Kirschner [ 13-Jul-2010 ]

Changing components to "Other", to allow for more accurate bug counts within each component

Comment by Steve Swinsburg [ 02-Nov-2010 ]

Marking this issue as Won't Fix as we do not have the resources to fix this. The workaround of specifying the extra JAVA_OPTS is suitable.

Comment by Anthony Whyte [ 16-Nov-2010 ]

Setting fix version to unknown.

Generated at Mon Feb 17 21:46:17 CST 2020 using Jira 8.0.3#800011-sha1:073e8b433c2c0e389c609c14a045ffa7abaca10d.