yes .. The JDk running in my environment is JDk1.7 . I think jetty-all 9.11 version needs JDK1.8.
Also I'm using org.eclipse.jetty.server.ServerConnector in Jetty9 to replace org.mortbay.jetty.SocketListener in Jetty5 to connect. Thanks On Tue, Aug 11, 2015 at 9:55 PM, Arun Kumar <[email protected]> wrote: > Hi Joakim, > > I have deployed the code build using Jetty-all 9.jar and getting this > error. Previously the application was running on Jetty5(Mortbay). Now it is > referring to Jetty9 eclipse classes. I have copied Jetty-all9.jar into lib. > > -------------------------------------------------------------------------------------------------------------------- > > org/eclipse/jetty/server/Connector : Unsupported major.minor version 52.0 > > End user message : Jetty could not be started. Check nested exceptions > following this for reason > > [0] : java.lang.UnsupportedClassVersionError: > org/eclipse/jetty/server/Connector : Unsupported major.minor version 52.0 > > [1] : Jetty could not be started. Check nested exceptions following this > for reason > Caused by: java.lang.UnsupportedClassVersionError: > org/eclipse/jetty/server/Connector : > > Could you please help ?. > > Thanks > > On Mon, Aug 10, 2015 at 11:11 PM, Joakim Erdfelt <[email protected]> > wrote: > >> If you can, use normal Jetty dependencies, *NOT* jetty-all. >> Next, use something a bit more current. >> Either Jetty 9.2.13.v20150730 (for Java 7) or Jetty 9.3.2.v20150730 (for >> Java 8 and HTTP/2 support) >> >> Also note, that there is no drop-in replacement for Jetty 6 to Jetty 9. >> The project moved from codehaus.org (which doesn't exist anymore) to >> eclipse.org >> In the process the namespace changed from org.mortbay.jetty to >> org.eclipse.jetty >> So if you depend on Jetty classes somewhere in your code, you'll have to >> do some code updates. >> >> If this is a jetty-distribution update, then you'll be better off using >> the new ${jetty.base} concepts, as that is far far easier to manage and >> maintain then the old techniques of updating jars, configurations, xmls, >> etc ... >> >> >> Joakim Erdfelt / [email protected] >> >> On Mon, Aug 10, 2015 at 9:41 AM, Arun Kumar <[email protected]> >> wrote: >> >>> Hi Friends, >>> >>> I'm migrating the application from Jetty 6.1.19 to Jetty-all-9.1. I'm >>> able to surpass all the compile errors in Jetty-9 and able to build and >>> deploy. During this migration I have removed all the Jetty6 jars from lib >>> and placed Jetty-all. 9 jar. Is this correct that only Jetty6 jars >>> replaced with Jetty9 OR Do I need to any other files ? >>> >>> My application is using Spring 3. jars also. >>> >>> Thanks >>> >>> _______________________________________________ >>> jetty-users mailing list >>> [email protected] >>> To change your delivery options, retrieve your password, or unsubscribe >>> from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/jetty-users >>> >> >> >> _______________________________________________ >> jetty-users mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> > >
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
