title: Cache busting mechanism for Java/SpringMVC/Maven project
body: <p>A little background about the app that I'm working in: Spring MVC, Java EE Web application, Maven.</p>
  
  <p>Basically, what I'm looking for is a mechanism to refresh all JS and CSS files upon each deployment of our application. As it stands right now, the application is referencing static files (e.g. "js/app.js"). Every time there is a change to this file, after redeploying locally, we get a 304 when the browser goes to download it (file has not been modified). My questions are:</p>
  
  <p>1) Would it be better to serve these files up again upon redeployment of application and use maybe the application version as a cache busting mechanism (e.g. "js/v1.0.0/app.js").  This can maybe be done via a servlet filter.</p>
  
  <p>2) Since the project is a maven dynamic web project, is there some sort of plugin that does this sort of thing.  I was looking at wro4j to see if it can do this, but from the very little I read about it, it's mostly used to handle minification of these JS and CSS, which is something also very useful.</p>
  
  <p>Which is the right approach? Thanks in advance</p>