[
https://issues.apache.org/jira/browse/WICKET-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090430#comment-13090430
]
Martin Grigorov commented on WICKET-3987:
-----------------------------------------
I think this is possible with custom caching strategy (see last comment by
Peter above). Your custom strategy can do nothing in
org.apache.wicket.request.resource.caching.IResourceCachingStrategy.decorateUrl(ResourceUrl,
IStaticCacheableResource) for the resources you decide.
> setUseTimestampOnResources and PackageResourceReference#getLastModified
> removed
> -------------------------------------------------------------------------------
>
> Key: WICKET-3987
> URL: https://issues.apache.org/jira/browse/WICKET-3987
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.0
> Environment: 1.5.0 trunk
> Reporter: Konstantin Ignatyev
> Assignee: Peter Ertl
>
> IResourceSettings#setUseTimestampOnResources and
> PackageResourceReference#getLastModified removed in the trunk breaking some
> of my components which rendered JScript reference from a component package.
> Now URL has timestamp and therefore parts of JScript relying on relative to
> the script positions of assets stopped working.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
