December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-14668) In case of 404, display the actual URL (in case of redirection)

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14668?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-14668: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > In case of 404, display the actual URL (in case of redirection) > --------------------------------------------------------------- > > Key: JBIDE-14668 > URL: https://issues.jboss.org/browse/JBIDE-14668 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: livereload > Affects Versions: 4.1.0.Beta1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha2 > > > For example, if the index.html page contains the following code: > {code} > <html> > <head> > <meta http-equiv="Refresh" content="0; URL=index.jsf"> > </head> > </html> > {code} > then the LiveReload server will first serve the index.html page and the browser will then redirect to index.jsf which does not exist as a file, which ends up with a 404 error from the server, but the user may not be aware of the redirect and think that the LiveReload server does not work as expected... -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14513) Improve the descriptions in the sections of the LiveReload server configuration editor

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14513?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-14513: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Improve the descriptions in the sections of the LiveReload server configuration editor > -------------------------------------------------------------------------------------- > > Key: JBIDE-14513 > URL: https://issues.jboss.org/browse/JBIDE-14513 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: livereload > Affects Versions: 4.1.0.Beta1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha2 > > > Descriptions should be: > {quote} > Configuration for embedded LiveReload server. Use <a href="http://firefox.com">Firefox</a> or <a href="http://chrome.com">Chrome</a> browser extensions to connect to it. > {quote} > and > {quote} > Configuration for optional LiveReload Proxy server. The proxy server allows you to access files from remote devices, inject livereload.js script for autoreload for browsers without the LiveReload browser extension. > {quote} > with wrapping and hyperlink pointings to download pages for each browser extension. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14948) Avoid unnecessary reload when BrowserSim targets another site (eg : example.com)

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14948?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-14948: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Avoid unnecessary reload when BrowserSim targets another site (eg : example.com) > -------------------------------------------------------------------------------- > > Key: JBIDE-14948 > URL: https://issues.jboss.org/browse/JBIDE-14948 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha2 > > > see comments on JBIDE-14827 -- 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, 7 months

1
0
0 / 0

[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: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > 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.0.Alpha2 > > > 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14950) Support remote servers

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14950?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-14950: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Support remote servers > ---------------------- > > Key: JBIDE-14950 > URL: https://issues.jboss.org/browse/JBIDE-14950 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha2 > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14295) Should livereload clients always get all notifications ?

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14295?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-14295: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Should livereload clients always get all notifications ? > -------------------------------------------------------- > > Key: JBIDE-14295 > URL: https://issues.jboss.org/browse/JBIDE-14295 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha2 > > > From [~yradtsevich]: > livereload works great with cordovasim right now because livereload always sends *any* change to *all* livereload clients even if they are not interested. > That is great for cordovasim, but is this expected ? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15966) Livereload does not work with HTML files without <html>

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15966?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15966: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Livereload does not work with HTML files without <html> > ------------------------------------------------------- > > Key: JBIDE-15966 > URL: https://issues.jboss.org/browse/JBIDE-15966 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.2.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha2 > > > Liveroload does not update HTML files if it does not have <html> tag which is not required by HTML5 spec in most cases: > http://www.w3.org/TR/2011/WD-html5-20110525/syntax.html#optional-tags > "An html element's start tag may be omitted if the first thing inside the html element is not a comment." > So livereload should handle all optional tags. And maybe log a worning (or rise an warning dialog?) if there is no valid HTML5 content at all and we can't insert JS links. -- 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, 7 months

1
0
0 / 0

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

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14999?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-14999: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > 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.Alpha2 > > > 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16217) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [LiveReload]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16217?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16217: ------------------------------- Parent: (was: JBIDE-15437) Issue Type: Task (was: Sub-task) > For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [LiveReload] > --------------------------------------------------------- > > Key: JBIDE-16217 > URL: https://issues.jboss.org/browse/JBIDE-16217 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.2.0.Alpha1 > > > For JBIDE 4.2.0.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1 > 1. Ensure your component features/plugins have been properly upversioned, eg., from 1.0.0 to 1.0.1 or 1.1.0. > {code}mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT{code} > 2. Update your root pom to use parent pom version 4.1.1.Beta1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1-SNAPSHOT; > {code}mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged){code} > 4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.2.0.Alpha1x branch; > {code}git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Alpha1x > git push origin jbosstools-4.2.0.Alpha1x{code} > 5. Close (not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%29...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%29...] -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16219) Errors about Hibernate console configuration, with no easy way to resolve

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16219?page=com.atlassian.jira.plugi... ] Pete Muir updated JBIDE-16219: ------------------------------ Attachment: kitchensink-angularjs-good.zip kitchensink-angularjs-bad.zip > Errors about Hibernate console configuration, with no easy way to resolve > ------------------------------------------------------------------------- > > Key: JBIDE-16219 > URL: https://issues.jboss.org/browse/JBIDE-16219 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Environment: JBDS 7.0.1.GA > Reporter: Pete Muir > Attachments: kitchensink-angularjs-bad.zip, kitchensink-angularjs-good.zip > > > In my case, this appears to be caused by existing dot-files (which were created by a previous version of JBDS, on Maven Import...). Removing those files and reimporting fixes the problem. > I haven't tested whether newer dot-files will cause the problem, or not. > Attached are two projects, one which shows the problem, and one that doesn't (clean dot-files generated). -- 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, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2013