You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Christoph Leiter (Updated) (JIRA)" <ji...@apache.org> on 2012/02/06 14:06:00 UTC

[jira] [Updated] (WICKET-4242) Detect new Markup Files in Development Mode

     [ https://issues.apache.org/jira/browse/WICKET-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christoph Leiter updated WICKET-4242:
-------------------------------------

    Comment: was deleted

(was: If you override MarkupCache#onMarkupNotFound() be sure to use ResourceStreamLocator instead of the default CachingResourceStreamLocator.)
    
> Detect new Markup Files in Development Mode
> -------------------------------------------
>
>                 Key: WICKET-4242
>                 URL: https://issues.apache.org/jira/browse/WICKET-4242
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.5.3
>            Reporter: bernard
>
> An extension of http://www.wicketframework.org/faqs.html#how-reload-changed-markup-files
> Let Wicket detect new markup files not only modifications to existing ones.
> This is useful if a developer fails to add a markup file. That causes an exception. Currently the application has to be re-deployed to fix this condition.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira