[
https://issues.apache.org/jira/browse/WICKET-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839820#comment-17839820
]
Martin Tzvetanov Grigorov edited comment on WICKET-7106 at 4/22/24 7:03 PM:
----------------------------------------------------------------------------
Please take a look at https://issues.apache.org/jira/browse/WICKET-7090.
Wicket uses IResourceCachingStrategy to generate the -ver-1001 part of the
ResourceReferences' names.
You may use even a custom impl to generate a unique value without waiting for a
new Wicket release.
The discussion at dev@ is
https://lists.apache.org/thread/drdsskl7nhj2xdrtk2z87p8f4v8c9w7r
was (Author: mgrigorov):
Please take a look at https://issues.apache.org/jira/browse/WICKET-7090.
Wicket uses IResourceCachingStrategy to generate the -ver-1001 part of the
ResourceReferences' names.
You may use even a custom impl to generate a unique value without waiting for a
new Wicket release.
> Changes in JS File between milestone and final release are cached by browsers
> -----------------------------------------------------------------------------
>
> Key: WICKET-7106
> URL: https://issues.apache.org/jira/browse/WICKET-7106
> Project: Wicket
> Issue Type: Wish
> Affects Versions: 10.0.0
> Reporter: Alexander Ermer
> Priority: Trivial
>
> My issue is the latest change of wicket-ajax-jquery.js between 10.0.0-M2 and
> 10.0.0 (final) from
> https://github.com/apache/wicket/commit/653d31b1154450626fc8c4047a6b25007924bf90
>
> We had to go in production with the milestone version which serves the file
> wicket-ajax-jquery-ver-1000.js. The exakt same filename is served by the
> final releaes BUT there are changes. Default browser settings do cache these
> files which leads to undefined function calls of `Wicket.Event.requestSubmit`.
>
> This issue is very easy to solve: please just release a version like 10.0.1
> without any changes. That way the file wicket-ajax-jquery-ver-1001.js would
> be served and my problems are gone.
>
> Thanks!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
