[jira] [Commented] (WICKET-3891) in development mode Wicket stops picking up markup changes

["Robert McGuinness (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064237#comment-13064237 ] 

Robert McGuinness commented on WICKET-3891:
-------------------------------------------

Is it similar to https://issues.apache.org/jira/browse/WICKET-3878?

> in development mode Wicket stops picking up markup changes
> ----------------------------------------------------------
>
>                 Key: WICKET-3891
>                 URL: https://issues.apache.org/jira/browse/WICKET-3891
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core
>    Affects Versions: 1.5-RC5.1
>         Environment: OS X 
>            Reporter: Konstantin Ignatyev
>
> I have wicket application running via mvn jetty:run under JRebel to facilitate code hotswap.
> With 1.5RC5.1 Wicket does not pick markup changes unless I change requested version, and it still put version on URL even I have getPageSettings.setVersionPagesByDefault(false); , but that is a minor inconvenience.
> More annoying that after awhile Wicket stops picking up changes in the markup of components used on my page. I mean that I can change markup for my components and it gets reflected upon page refresh (with requesting non existent version), but at some point it stops, changes to the markup of subcomponents are not picked up.
> That forces me to restart application, which is major productivity killer....

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira