They run the same IBM JVM, with version 1.5.0. Putty was using gradle 0.3, and when I changed to 0.6.1 it solved the major.minor version problem.
Still, when I run the build locally everything works fine. With the same gradle distribution and the same jdk on the unix blade, the same project has an RMI Compiler error during EJB deploys because RepositoryId cannot be found. I've compared the debug output for both. The classpaths and properties set are almost identical, so I don't understand why one fails. Anyone have any experience with EJBs, specifically with deploying them outside of websphere (using the wsejbdeploy ant task)? Anyone know where to look? Jacob Grydholt Jensen wrote: > > 2009/7/9 JerodLass <[email protected]>: >> >> Now I seem to be seeing this problem a lot: >> The java class could not be loaded. >> java.lang.UnsupportedClassVersionError: >> org/gradle/BootstrapMain (Unsupported major.minor version 49.0) >> When I try to run gradle commands. The same command runs from hudson cis >> but not from a putty terminal. What causes this issue? >> > > Normally, that you are running 1.5 code with a 1.4 JVM. I would > imagine that Hudson is running >= 1.5 JVM while your putty session > uses a 1.4 JVM. > > Best regards, > Jacob Grydholt > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > -- View this message in context: http://www.nabble.com/Deploying-EJBs-tp24398697p24485542.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
