[WICKET-7090] Files in release jars do not have a modification timestamp set

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 9.8.0, 9.9.0, 9.10.0, 9.11.0, 9.12.0, 9.13.0, 9.14.0, 9.15.0, 9.16.0
• Fix Version/s: 10.0.0
• Component/s: release
• Assignee: Emond Papegaaij
• Reporter: Emond Papegaaij
• Created: 07/Dec/23 07:41
• Updated: 10/Jan/24 18:56
• Resolved: 10/Jan/24 09:07

Description

Starting with 9.8.0, the release jars are built with file entries without a last modification timestamp. This can cause issues if LastModifiedResourceVersion used for the resourceCachingStrategy. The browser may be using an older version of the resource, even if a newer version is available. This strategy is normally only used in development mode, but even then this can cause unexpected behavior.

As discussed on the dev list, the best we can do is to set the last modification timestamp to fixed time during the release, as git doesn't track this. A suggestion is to use  the project.build.outputTimestamp property: https://maven.apache.org/guides/mini/guide-reproducible-builds.html

Issue Links

• links to: GitHub Pull Request #758