Hi, With the upgrade to wicket 9.16.0 we've seen some issues with the new 'Wicket.Event.requestSubmit' method that was added to wicket-ajax-jquery. It turns out that a cached version of the resource was used, and this seems to be caused by an incorrect version string in the url. The filename is rendered as 'wicket-ajax-jquery-ver-318207600000.js'. The same is true for JQuery: 'jquery-3.7.1-ver-318207600000.js'. This seems to be caused by an incorrect modification time in the jar. Our repository shows all files in the wickets jars to have the timestamp 318211200000. Other resources (not from wicket itself) do have correct timestamps.
This seems to be the case since wicket 9.8.0. Versions prior to that have correct timestamps. Did something change to the way wicket is built between 9.7.0 and 9.8.0? I can't find anything related in the commits. We can switch from LastModifiedResourceVersion to something else in our applications to work around this issue, but maybe we should consider tracking down this issue and release a 9.16.1. I'd expect we are not the only ones using LastModifiedResourceVersion. Best regards, Emond
