On 10/11/2007, Rahul Akolkar (JIRA) <[EMAIL PROTECTED]> wrote: > > [ > https://issues.apache.org/jira/browse/JEXL-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Rahul Akolkar resolved JEXL-38. > ------------------------------- > > Resolution: Fixed > > All that is cruft.
OK, sorry did not check that they were referenced. > Each of those pages were deployed between May 06 and June 07 (the latest site > was deployed yesterday, those pages are no longer gen'ed, and therefore it > shouldn't be possible to navigate to them directly -- save web search results > and such). Perhaps some <reports> were removed from the site, some changed > formats etc. Such pages could be rm'ed from /www/cao/* if there is consensus. If they are not in the current deployment, then is consensus needed? Seems to me that the deployment procedure needs tweaking to ensure that the pages on the server correspond with what is generated.and deployed. For example, by deploying to a temporary directory, and then switching top-level directories. [Or removing the existing content before deployment - not recommended!] Other sites may use SVN, in which case it's easier to find which files should not be there. > Generally speaking, this is a larger problem than [jexl] (if you move the > grep up to /w3/cao, I suspect you will get a staggering number of hits). Indeed, but that does not mean they should all be ignored ... One possible work-round in the meantime might be to provide redirects - if that can be done without impacting HttpComponents. <snip/> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
