|
Java 5 woes: msg#00655cms.sakai.devel
I went ahead and ran the OS X update to get Java 5 as the default. I was worried that it would cause problems (our production servers still run JVM 1.4.2) and it has. I updated my build.properties with maven.compile.source=1.4 and maven.compile.target=1.4, I set JAVA_HOME so it points to my older Java installation, and I even replaced the sym link for /usr/bin/javac. When I do a build on my machine it runs fine, but when I copy it up to one of our app servers, I get a wide variety of "Unsupported major.minor version 49.0" errors on a lot of classes, particularly every time a tool tries to load in an iframe. What have I overlooked? Is there a way to verify after the fact that my object files were indeed produced by the 1.4.2 compiler? regards, Zach A. Thomas Software Engineer Texas State University http://www.txstate.edu ---------------------- This automatic notification message was sent by Sakai Collab (http://collab.sakaiproject.org/portal) from the DG: Development site. You can modify how you receive notifications at My Workspace > Preferences. |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | RE: 2.2 mini build issue: 00655, Zeckoski, Aaron |
|---|---|
| Next by Date: | Re: 2.2 mini build issue: 00655, Ray Davis |
| Previous by Thread: | Twin Peaks?i: 00655, Patricia Goldweic |
| Next by Thread: | Re: Java 5 woes: 00655, Steven Githens |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |