Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Jetty plugin not serving resources

See original GitHub issue

The Jetty plugin when executing mvn jetty:run by default only serves src/main/webapp (also it seems ${project.output.directory}/webapp-tmp) as static resources.

The app theme files are copied only ${project.build.outputDirectory}/META-INF/resources which is served as per the Servlet 3.0 specification.

A fix for running jetty should be found other than requiring adding the plugin configuration

<webApp>
  <resourceBases> 
    <resourceBase>${project.build.outputDirectory}/META-INF/resources</resourceBase>
  </resourceBases>
</webApp>

Issue Analytics

State:
Created 3 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

caaladorcommented, Nov 18, 2020

I guess the best way to go is to have the static files go to VAADIN/static and serve them from there by ourselves as then we do not need to care about jar vs war.

0reactions

plekucommented, Dec 7, 2020

Reopened to figure out how we can get any resources from the theme folder to work with using an url with path "/theme/my-theme/something.png" from Java or CSS regardless of the app packaging or used server. Currently it is possible to use relative paths in css and this part is handled by webpack and will work even after this copying.

Lets use #9535 for the implementation.