You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, this problem does not appear in the case of Spring Boot 3.1.5
What I do here is to serve static content from the src\main\resources\static path.
Static content is generated with angular-cli v17, which is a simple project.
I created two simple examples, one with Spring Boot 3.1.5 in which the problem does not appear and works correctly,
and one with Spring Boot 3.2.0 RC2 in which this problem can be observed.
This problem only occurs after the project is assembled with .\gradlew clean assemble and is run with java -jar .\app-sample-sb320-rc2-issue-0.0.1-SNAPSHOT.jar
In the project app-sample-sb320-rc2-issue.zip, you will find in the root, the issue-details directory, which in turn contains files:
Thanks for the report and sample app. This appears to be a regression caused by the new nested jar support. The problem does not occur if you switch back to the old support by adding the following to build.gradle:
philwebb
changed the title
Spring Boot 3.2.0 RC2 Issue - Serve static content FileNotFoundException: class path resource [static/styles-5INURTSO.css] cannot be resolved in the file system for checking its last-modified timestamp
FileNotFoundException thrown serving class path resources due to JarUrlConnection.getLastModified() returning 0
Nov 5, 2023
philwebb
changed the title
FileNotFoundException thrown serving class path resources due to JarUrlConnection.getLastModified() returning 0
FileNotFoundException is thrown serving resources due to JarUrlConnection.getLastModified() returning zero
Nov 5, 2023
@adora-tech Thanks so much for finding and raising this one before we released 3.2.0. The sample was super helpful and I think I've identified and fixed the underlying problem.
Re-opening as some of the new tests are failing on Windows. It looks like a file handle's being leaked which prevents the jar from being deleted during cleanup.
Hello,
First, this problem does not appear in the case of Spring Boot 3.1.5
What I do here is to serve static content from the
src\main\resources\static
path.Static content is generated with angular-cli v17, which is a simple project.
I created two simple examples, one with Spring Boot 3.1.5 in which the problem does not appear and works correctly,
and one with Spring Boot 3.2.0 RC2 in which this problem can be observed.
This problem only occurs after the project is assembled with
.\gradlew clean assemble
and is run withjava -jar .\app-sample-sb320-rc2-issue-0.0.1-SNAPSHOT.jar
In the project app-sample-sb320-rc2-issue.zip, you will find in the root, the
issue-details
directory, which in turn contains files:browser-access-issue.png
log-acces-issue.txt
Attached you will find the two archived projects:
app-sample-sb315-working.zip
app-sample-sb320-rc2-issue.zip
Thank you,
Iulius Ciorica
The text was updated successfully, but these errors were encountered: