Is this something you need in production? If not, just set the
production-mode symbol to false.
I think backporting the 5.4 way of handling asset URLs would be quite a lot
of work.
On Sep 9, 2015 3:14 AM, "Poggenpohl, Daniel" <
daniel.poggenp...@isst.fraunhofer.de> wrote:
> Hi,
>
> I see that gen
Hi,
I see that generating hash urls for Tapestry assets is only done since Tapestry
5.4. Since I have a caching problem at the moment because my javascript and css
files regularly change in the phase we're in, the "identify asset by app
version" strategy is very inconvient, to say the least.
C
