[
https://issues.apache.org/jira/browse/WICKET-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091177#comment-13091177
]
Konstantin Ignatyev commented on WICKET-3987:
---------------------------------------------
Just an idea: how about treating a jar as versioned resource? For example in my
case that would work beautifully: my star rating component was in its own jar
file, so everything would have the same version somewhere above, and all the
relative URLs would resolve just fine. Since jar is pretty much invisible at
runtime maybe we can have some version marker inside package, and then version
in the URL can be at the level, so all other relative URLs inside package would
work fine below that level.
That might make sense for other cases: for example a skin for application where
bunch of images and css and scripts can be packaged.
> 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
