[jbosstools-issues] [JBoss JIRA] (JBIDE-14999) LiveReload: add option for refresh delay

Xavier Coulon (JIRA) jira-events at lists.jboss.org
Tue Jul 2 04:11:25 EDT 2013


     [ https://issues.jboss.org/browse/JBIDE-14999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xavier Coulon reassigned JBIDE-14999:
-------------------------------------

    Assignee: Xavier Coulon

    
> LiveReload: add option for refresh delay
> ----------------------------------------
>
>                 Key: JBIDE-14999
>                 URL: https://issues.jboss.org/browse/JBIDE-14999
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: livereload
>    Affects Versions: 4.1.0.Beta1
>            Reporter: Lukáš Fryč
>            Assignee: Xavier Coulon
>             Fix For: 4.2.0.Alpha1
>
>
> LiveReload currently refreshes a page immediately as changes are deployed (at least I guess so).
> However it takes some time to WildFly container, JRebel or JSF implementation to reflect those changes. I'm getting following error:
> {code}
> Warning: This page calls for XML namespace http://jsflive.at/taglib declared with prefix jl but no taglibrary exists for that namespace.
> {code}
> That means the taglibrary configuration in JSF subsystem wasn't initialized correctly (seems like a consequence of JRebel configuration reloading):
> {code}
> 11:10:19,153 INFO  [stdout] (default task-46) 2013-06-25 11:10:19 JRebel: Reloading configuration
> {code}
> I propose to add a "refresh delay" which will serve as a delay for runtime to reflect changes and which will be configurable by user considering his use case.
> For record, I have tried to use command line guard-livereload with following configuration with 2 sec. grace period and everything works fine then - changes are reflected after delayed update:
> {code}
> guard 'livereload', :grace_period => 2 do
>    watch(%r{.+\.(css|js|html|xhtml|json)})
> end
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the jbosstools-issues mailing list