You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Emond Papegaaij (Jira)" <ji...@apache.org> on 2024/01/10 09:08:00 UTC
[jira] [Resolved] (WICKET-7090) Files in release jars do not have a modification timestamp set
[ https://issues.apache.org/jira/browse/WICKET-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emond Papegaaij resolved WICKET-7090.
-------------------------------------
Fix Version/s: 10.0.0-M3
Resolution: Fixed
> Files in release jars do not have a modification timestamp set
> --------------------------------------------------------------
>
> Key: WICKET-7090
> URL: https://issues.apache.org/jira/browse/WICKET-7090
> Project: Wicket
> Issue Type: Bug
> Components: release
> Affects Versions: 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
> Reporter: Emond Papegaaij
> Assignee: Emond Papegaaij
> Priority: Minor
> Fix For: 10.0.0-M3
>
>
> 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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)