[
https://issues.apache.org/jira/browse/TAPESTRY-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-1918.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.7
Again, this is a quick but not perfect fix but I'm satisfied that it will work
for most people. The worst will be for message catalog files, as it is more
common to go from 0 to 1 of those files (which may not be picked up) than to go
from n to m of them (which is more generally what the fix detects).
> Tapestry's reload logic should be able to see additions, not just deletions
> and changes
> ---------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1918
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1918
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.6
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.7
>
>
> Tapestry has change monitoring logic for templates, classes and properties
> files. However, that change logic is only aware of changes to loaded files,
> and of deletion of loaded files. It would be nice if Tapestry was aware of
> the folders containing tracked files, and was capable of identifying when
> files were added as well. This shows up in development, when creating a new
> page class in a running application still gives a "page not found" exception,
> because Tapestry is not aware of the new class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
