> > > > https://github.com/apache/wicket/blob/a68536eb095bb5cf59e4063b6af9436523ddc623/wicket-core/src/main/java/org/apache/wicket/settings/ResourceSettings.java#L650-L664 > LastModifiedResourceVersion is used in DEV mode by default. > MessageDigestResourceVersion is for PROD. >
Yes, I know. I don't know why we ever configured our applications to always use LastModifiedResourceVersion, but this was working fine for us, until wicket 9.8.0. Something changed that caused the timestamps to be reset at that time. I think we should try to find out what caused this, and fix it. As you said LastModifiedResourceVersion is used by default in dev mode, and it is currently broken. I'll create a Jira issue for this tomorrow, I didn't have the time for it today. For us, I've already recommended everyone to remove our custom configuration of this setting. The default makes much more sense, and only developers will be faced with a possible invalid cache entry. Best regards, Emond >
