[jbosstools-issues] [JBoss JIRA] (JBIDE-14964) LiveReload doesn't reload when JRebel is used, so resources are "never published automatically"
Max Rydahl Andersen (JIRA)
jira-events at lists.jboss.org
Tue Jul 2 04:55:22 EDT 2013
[ https://issues.jboss.org/browse/JBIDE-14964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786802#comment-12786802 ]
Max Rydahl Andersen commented on JBIDE-14964:
---------------------------------------------
this one is tricky to support - we'll need to detect never publish is enabled AND jrebel is active to know what to do :/
> LiveReload doesn't reload when JRebel is used, so 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.1.1.Final, 4.2.0.Alpha1
>
>
> 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.
--
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