jetty / jetty.project

Eclipse Jetty® - Web Container & Clients - supports HTTP/2, HTTP/1.1, HTTP/1.0, websocket, servlets, and more
https://eclipse.dev/jetty
Other
3.86k stars 1.91k forks source link

No hot deployment when replacing war-file #12543

Open lglowania opened 3 hours ago

lglowania commented 3 hours ago

Jetty version(s) 12.0.15

Jetty Environment ee10

Java version/vendor (use: java -version) openjdk version "21.0.5" 2024-10-15 LTS

OS type/version Debian Bookworm

Description In our setup we copy war-archives to our production-system to deploy new versions of our software. With Jetty 11 the new war-archive was detected and the context was redeployed. Since the upgrade to Jetty 12.0.10, i always have to touch the context's virtual-host-xml-file to trigger redeployment.

How to reproduce? Create a webapp with the following structure in the webapps folder and enable the ee10-deploy-module.

webapps/my-webapp.xml
webapps/my-webapp.war

The webapp is only redeployed when my-webapp.xml is touched but not when my-webapp.war ist touched.

joakime commented 3 hours ago

Hmm. Your report does indeed look like a regression. Do you also have a webapps/my-webapp.properties file? (usually used to specify the environment to deploy to)

lglowania commented 2 hours ago

No, i have no my-webapp.properties-file.