When I run jetty from Eclipse using eclipse-jetty-plugin on eclipse latest mars jetty version from the 9.2.11 I am experiencing issue with classpath on the jvm that is created.
I am using the "Use jetty at path" option where i use my own jetty home location.
Here is my JVM's --classpath when I run the the jetty java executable from eclipse. It gets truncated due to big length:
Notice the end of that how the string is getting too long for it to handle.
1) I think the plugin should smart enough to grab jetty runner and use that instead of trying to make a huge classpath. i.e. -jar /home/ndipiazza/Downloads/jetty-distribution-9.2.11.v20150529/jetty-runner-9.2.11.v20150529.jar
2) Even if 1) is something you are not willing to do... Then the classpath should not be getting truncated on Linux systems. Windows yeah, but not linux or mac.
i will make my installation names shorter for now to get passed this bug.
When I run jetty from Eclipse using eclipse-jetty-plugin on eclipse latest mars jetty version from the 9.2.11 I am experiencing issue with classpath on the jvm that is created.
I am using the "Use jetty at path" option where i use my own jetty home location.
Here is my JVM's --classpath when I run the the jetty java executable from eclipse. It gets truncated due to big length:
Notice the end of that how the string is getting too long for it to handle.
1) I think the plugin should smart enough to grab jetty runner and use that instead of trying to make a huge classpath. i.e.
-jar /home/ndipiazza/Downloads/jetty-distribution-9.2.11.v20150529/jetty-runner-9.2.11.v20150529.jar
2) Even if 1) is something you are not willing to do... Then the classpath should not be getting truncated on Linux systems. Windows yeah, but not linux or mac.i will make my installation names shorter for now to get passed this bug.