Anonymous | Login | Signup for a new account | 11-21-2024 22:39 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0001488 | [Resin] | minor | always | 12-04-06 10:17 | 06-04-07 14:44 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | |||||||
Summary | 0001488: merge path dependency checking | ||||||||
Description |
(rep by Kimberly Nicholls) I am using rewrite-real-path with the merge scheme in resin 3.0.21. Here's a sample from my config file: <rewrite-real-path> <real-path regexp="^/merge/comp" target="merge:(custom/comp;standard/comp)"/> </rewrite-real-path> This works great if I have a standard/comp/test.jsp file but not a custom/comp/test.jsp. But when I add custom/comp/test.jsp, resin doesn't use it -- it keeps using standard/comp/test.jsp. I have tried forcing a recompile by deleting all generated files that include test.jsp, but it still uses the standard/comp/test.jsp. It does find the new file if I delete all of the generated files and restart the server. It seems like it's caching the merge path results somewhere. Is restarting the only way to clear this, or is there some way I can force it to recalculate the merge list? |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
There are no notes attached to this issue. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
26 total queries executed. 24 unique queries executed. |