[
https://issues.jboss.org/browse/JBIDE-14964?page=com.atlassian.jira.plugi...
]
Lukáš Fryč updated JBIDE-14964:
-------------------------------
Description:
When JRebel is used together with LiveReload, "Never Publish Automatically"
needs to be turned on in Publishing setup of Server Runtime (AS/EAP) settings.
In this mode, LiveReload does not work, because new resources are never published
according to the IDE.
However JRebel reloads those resources in a background.
----
In the opposite case ("Automatically publish after resource change"), I'm
getting "Concurrent resource modification" error occasionally.
was:
When JRebel is used together with LiveReload, "Never Publish Automatically"
needs to be checked in Publishing setup of Server Runtime (AS/EAP) settings.
In this mode, LiveReload does not work, because new resources are never published
according to the IDE.
However JRebel reloads those resources in a background.
----
In the opposite case ("Automatically publish after resource change"), I'm
getting "Concurrent resource modification" error occasionally.
LiveReload doesn't reload when JRebel is used, because resources
are "never published automatically"
----------------------------------------------------------------------------------------------------
Key: JBIDE-14964
URL:
https://issues.jboss.org/browse/JBIDE-14964
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: livereload
Affects Versions: 4.1.0.Beta1
Reporter: Lukáš Fryč
Assignee: Xavier Coulon
Priority: Critical
Fix For: 4.2.x
When JRebel is used together with LiveReload, "Never Publish Automatically"
needs to be turned on in Publishing setup of Server Runtime (AS/EAP) settings.
In this mode, LiveReload does not work, because new resources are never published
according to the IDE.
However JRebel reloads those resources in a background.
----
In the opposite case ("Automatically publish after resource change"), I'm
getting "Concurrent resource modification" error occasionally.
--
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