[ http://issues.apache.org/jira/browse/MYFACES-1118?page=comments#action_12366389 ]
Mathias Broekelmann commented on MYFACES-1118: ---------------------------------------------- Resource caching still works. It is done by a timestamp held in the application scope. The timestamp will be renewed in every deployment of the webapp. See org.apache.myfaces.renderkit.html.util.DefaultAddResource.getCacheKey(...). If lastModified is not found the current system time will be used for the inital value. I think that behavior is ok. Is it ok to remove the obsolete property file? > DefaultAddResource cache disabled because of the Maven build > ------------------------------------------------------------ > > Key: MYFACES-1118 > URL: http://issues.apache.org/jira/browse/MYFACES-1118 > Project: MyFaces > Type: Bug > Components: Tomahawk > Versions: Nightly > Reporter: Sylvain Vieujot > > Since the build is done by Maven, the ant code that was parsing the > commons/src/main/resources/org/apache/myfaces/renderkit/html/util/AddResource.properties > by replacing the @lastModified@ tag with the build date is gone. > So the file in the jar now contains > [EMAIL PROTECTED]@ > instead of something like : > lastModified=2006-02-14 23:47:48 +0400 > The effect of this is that the resource files aren't cached anymore. > I'm still very new to maven, so I don't know yet how to restore this in the > maven build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
