Thanks for the feedbacks guys, I just quickly took care about it, see MSKINS-61
best, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Wed, Aug 22, 2012 at 1:29 PM, Tony Chemit <[email protected]> wrote: > On Wed, 22 Aug 2012 13:22:56 +0200 > Olivier Lamy <[email protected]> wrote: > >> 2012/8/22 Simone Tripodi <[email protected]>: >> > Hi all guys, >> > >> > time ago Robert and I were discussing about versioning the produced >> > minified css/js to avoid browser cache conflicts, I mean, ATM all >> > fluido skin versions refer to >> > >> > $relativePath/js/apache-maven-fluido.min.js >> > $relativePath/js/apache-maven-fluido.min.cs >> > >> > that could cheat users when upgrading skins, since they could have >> > been cached by the browser and while rendering the site, the old >> > css/js could be used. >> > >> > I think it would be good versioning the produced resources according >> > to the current fluido skin version, such as >> > >> > $relativePath/js/apache-maven-fluido-${project.version}.min.js >> > $relativePath/js/apache-maven-fluido-${project.version}.min.cs >> > >> > WDYT? >> >> Definitely +1 ! > > +1 > > yes, as anything in life, versioning is a requirement (when two versions can > exist :)). > > > tony. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
