[JBoss JIRA] (JBIDE-14964) LiveReload doesn't reload when JRebel is used, because resources are "never published automatically"
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14964?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-14964:
---------------------------------------------
[~lfryc] what was your update about ? Can't spot it ;)
> 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 which might not be related to JRebel usage.
--
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
12 years, 1 month
[JBoss JIRA] (JBIDE-16657) handle the case where development = stable
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16657?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16657:
---------------------------------------------
this is not about the updatesite - it is about the website.
the website would say development updatesite contains 4.1.1.CR1 when it actually contains 4.1.1.Final.
Suggestion is when that happens have a marker on development download page to note that the updatesite now actually have final. (a comprimise between reality and clean separation on the website urls/content)
> handle the case where development = stable
> -------------------------------------------
>
> Key: JBIDE-16657
> URL: https://issues.jboss.org/browse/JBIDE-16657
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: website
> Reporter: Max Rydahl Andersen
> Fix For: 4.2.0.Beta1
>
>
> once we release Final, the development updatesite actually contains final and not the latest CR1 so there is a mismatch between website and reality ;)
> Suggestion:
> Add "marker" to latest_development in products.yml that will add an alert
> to the latest active development download that the updatesite actually has stable.
> actualcontent: 4.1.0.Final
> Would give something like:
> Info: 4.1.0.Final have been released and is what you will get when installing from the development update site.
--
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
12 years, 1 month