[
https://issues.apache.org/jira/browse/WICKET-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090363#comment-13090363
]
Konstantin Ignatyev commented on WICKET-3987:
---------------------------------------------
The approach implemented is a blanket one - what is removed is the ability to
selective remove versioning from a particular resource. I do not need timestamp
in particular, but a way to let wicket know that THIS resource should not use
versioned URL. IMO this is a valid use case. Please consider returning some
sort of marker method to ResourceReference to allow using custom versioning, or
no versioning at all.
> 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
