xsbt-web-plugin | Servlet support for sbt | Build Tool library
kandi X-RAY | xsbt-web-plugin Summary
kandi X-RAY | xsbt-web-plugin Summary
Servlet support for sbt
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of xsbt-web-plugin
xsbt-web-plugin Key Features
xsbt-web-plugin Examples and Code Snippets
Community Discussions
Trending Discussions on xsbt-web-plugin
QUESTION
I am running a scala 2.11.12 app on lift 3.3.0 built with sbt 1.3.8. I have tried 4.0.3 and 4.2.0 of xsbt-web-plugin. My app launches fine when I use jetty:start but when I use jetty:quickstart it fails to launch - I get a 500 error in the browser and when I check the application log in the console I see java.lang.NoSuchMethodError: 'int javax.servlet.http.HttpServletResponse.getStatus()' which causes the jetty instance to give back a 500.
** edit ive gone back further in my logile
What is the difference between how quickstart runs and how start runs? I cant figure out the problem.
Below is my build.sbt in case it helps. Below that Ive include the console logs for the request in jetty:quickstart showing the error Im getting. I dont get this error for jetty:start.
** edit 2 Ive jun jetty:start then show update, and jetty:quickstart then show update. They both have javax.servlet:servlet-api:2.5:default as a dependency. But jetty:start works fine and starts the container, while jetty:quickstart fails to initialize the container. I'm at a loss to understand why one works and one fails - it seems to me both should fail.
** edit 3 I figured out why servlet-api 2.5 was coming in, and have updated the paypal dependencies to fix that. I'd still love to know why jetty:start worked but jetty:quickstart didnt - they both seemingly should've failed.
build.sbt
...ANSWER
Answered 2020-Apr-25 at 22:50The jetty:start
and jetty:quickstart
commands both come from xsbt-web-plugin. Note that jetty:quickstart
is unrelated to the Quickstart Webapps feature of Jetty.
The main difference between the two is that start
builds a complete package of your project and quickstart
does not. With quickstart
, no .war file is created, your classes are not packaged up in a .jar file, etc.
With quickstart
, Jetty is run using your project's runtime classpath as managed by sbt. With start
, Jetty is run with only your project's package, and the dependencies it contains as .jar files. These can differ, as sbt's runtime classpath will include dependencies in the provided
scope, while your package will not. This is why one is working for you, and the other is not.
Your error:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install xsbt-web-plugin
The development cycle can be sped up by serving static resources directly from source, and avoiding packaging of compiled artifacts.
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page