Thank you! Exactly what I need!
Josh Canfield wrote:
Take a look at the TapestryModule.java. In
contributeClasspathAssetAliasManager there is now a version added to all the
classpath resources. You could do something similar with your app version.
http://tapestry.apache.org/tapestry5/apidocs/src-html/org/apache/tapestry5/services/TapestryModule.html#line.241
Then you just have to remember to up your version in one place...
Josh
On Thu, Aug 21, 2008 at 10:11 PM, Ivan Dubrov <[EMAIL PROTECTED]> wrote:
Hi,
With https://issues.apache.org/jira/browse/TAPESTRY-2159 issue fixed, I've
got a problem upgrading my application. Since Tapestry sets Expires header
to be far in the future, old JS/CSS are used after application upgrade. I
don't want to version my JS/CSS files, because it's too error-prone (I can
forget to do it) and this is an extra bookkeeping I want to avoid. Also,
versioning JS manually is not very VCS-friendly.
What I want, is that Tapestry somehow will add version automatically to the
URL. For example, reference to JS "app.js" will become something like
".../app.js/1.1" or ".../app.js/20080821" or anything else that changes
between application deployments. This should not be added to the manually
versioned resources, so there should be some configurability, I think.
What do you think? Do I have other options to resolve this issue?
--
WBR,
Ivan S. Dubrov
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
WBR,
Ivan S. Dubrov
