[ https://issues.jboss.org/browse/JBIDE-15080?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-15080. ----------------------------------------- Resolution: Rejected I'm going to reject this since its two different concerns. LiveReload consists of two parts - a LiveReload server and a LiveReload Client. The livereload client knows about which page is being loaded and contacts the server. The Livereload server listens to resource changes and send notifications to the clients that have asked for them. In Eclipse you are "in-the-middle", you are opening a resource target for livereload and because Eclipse knows about the exact server it can show this dialog and start the server before the browser is opened. In BrowserSim you are past that point - you are in the client and there is no contact to the server nor to eclipse from here that can be used sensibly to open this dialog. This is the exact same if you install the LiveReload plugin into your safari and chrome - when you enable livereload here you don't expect a dialog asking about the livereload server being started. Furthermore livereload could also be running as a standalone program (like guard-reload) and here browsersim would connect fine too - not needing this extra launch. -- 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