[
https://issues.apache.org/jira/browse/WICKET-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090581#comment-13090581
]
Peter Ertl commented on WICKET-3987:
------------------------------------
Technically a resource is something that responds to a request with some kind
of response to the client. A package is just a virtual location represented by
a file system folder or a jar file location. So it should be treated
differently from a resource. But I could imagine it makes sense to support
urlFor(...) to resolve a package location. However this has to be discussed
first and will not happen before 1.5.0 since we are almost gone final.
> 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
