[JBoss JIRA] (JBIDE-14964) LiveReload doesn't reload when JRebel is used, because resources are "never published automatically"
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14964?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-14964:
----------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> 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: LATER
>
>
> 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 was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months
[JBoss JIRA] (JBIDE-15073) LiveReload for workspace resources should be shown under 'Show In' in context menu
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15073?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-15073:
----------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> LiveReload for workspace resources should be shown under 'Show In' in context menu
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-15073
> URL: https://issues.jboss.org/browse/JBIDE-15073
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: livereload
> Affects Versions: 4.1.0.Beta2
> Reporter: Michelle Murray
> Assignee: Xavier Coulon
> Fix For: LATER
>
>
> For deployed apps, can right-click app in servers tab and click Show In > Web Browser via LiveReload Server. Easy :)
> For workspace resources, can right-click index.html file in project explorer tab and select Open With > Web Browser via LiveReload Server. But then if want to open file in editor have to click again Open With > JBoss Tools editor. So the file's default association with editors and browsers has to keep changing as I open it with LiveReload or an editor.
> A better workflow for workspace resources would be if can right-click index.html file in project explorer tab and select *Show In* > Web Browser via LiveReload Server. This would be good because:
> * Would match 'Show In' for deployed apps
> * Would leave association of file with one editor and double-clicking file would always result in opening in editor
> * Would mean not having to reset file association with editor after opening in browser with LiveReload server
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months
[JBoss JIRA] (JBIDE-19051) Show warning in case of ambiguous RESTful web services path
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19051?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-19051:
----------------------------------
Fix Version/s: 4.3.x
> Show warning in case of ambiguous RESTful web services path
> -----------------------------------------------------------
>
> Key: JBIDE-19051
> URL: https://issues.jboss.org/browse/JBIDE-19051
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.2.2.Final
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Priority: Minor
> Labels: jax-rs
> Fix For: 4.3.x
>
>
> If I have two classes which both follow same structure and there are some JAX-RS web services mapping to same path in JAX-RS Web Services node in Project Explorer, there should be warning on both such places where it occurs and in Problems view. Warning should be about ambigous path for JAX-RS web services.
> It's possible to have multiple items under JAX-RS Web Services node with same label.
> Even though there are strategies to resolve order of evaluating path, there could be some cases where it's not enough. And such solution could help developer to find out if there are such flaws in design.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months