[JBoss JIRA] (JBIDE-15613) Error: Failed to send reload command to browser
by Vlado Pakan (JIRA)
Vlado Pakan created JBIDE-15613:
-----------------------------------
Summary: Error: Failed to send reload command to browser
Key: JBIDE-15613
URL: https://issues.jboss.org/browse/JBIDE-15613
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: livereload
Affects Versions: 4.1.1.Alpha2
Environment: JBT Alpha2-v20131002-1827-B444, Linux 64bit, Java 6
Reporter: Vlado Pakan
Priority: Critical
Fix For: 4.1.1.Beta1
1. Import HTML 5 project from Central
2. Run it on server
3. Open project in Web Browser with LiveReload via Server View
4. Update and save index.html file many times
ASSERT: Changes to index.html are reflected in Web Browser
ERROR: This error appear in Error Log:
Failed to send reload command to browser
{noformat}
java.io.IOException: closedOut 1001:null
at org.eclipse.jetty.websocket.WebSocketConnectionRFC6455$WSFrameConnection.sendMessage(WebSocketConnectionRFC6455.java:437)
at org.jboss.tools.livereload.core.internal.server.jetty.LiveReloadWebSocket.sendMessage(LiveReloadWebSocket.java:97)
at org.jboss.tools.livereload.core.internal.server.jetty.LiveReloadWebSocket.inform(LiveReloadWebSocket.java:177)
at org.jboss.tools.livereload.core.internal.service.EventService.publish(EventService.java:57)
at org.jboss.tools.livereload.core.internal.service.ServerLifeCycleListener.publishFinished(ServerLifeCycleListener.java:131)
at org.eclipse.wst.server.core.internal.Server.firePublishFinished(Server.java:1150)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3176)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
{noformat}
--
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, 6 months
[JBoss JIRA] (JBIDE-15506) Support Asciidoctor files
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15506?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-15506 at 10/4/13 4:32 AM:
--------------------------------------------------------------
Not working with JBT Alpha2-v20131002-1827-B444 and Chrome Web Browser
1. Create new .asciidoc file
ERROR: File is automatically opened in Web Browser with LiveReload.js injected
Should be opened in JBT editor. It's empty file nothing to display in Web Browser
2. Open, edit and save file in JBT
3. Refresh file opened in Web Browser
ASSERT: File is properly displayed and aciidoc preview add-on works
4. Enable livereload add-on in Chrome
5. Update and save .asciidoc file in JBT more times
ERROR: Only first change to file is displayed within Chrome web browser
6. Reenable livereload add-on in chrome
ASSERT: File is refreshed
7. Open .asciidoc file in Chrome via file:/// protocol
ASSERT: Changes made to .asciidocfile via JBT are displayed in Chrome
ERROR: asciidoc preview add-on doesn't work for this file
was (Author: vpakan):
Not working with JBT Alpha2-v20131002-1827-B444 and Chrome Web Browser
1. Create new .asciidoc file
ERROR: File is automatically opened in Web Browser with LiveReload.js injected
Should be opened in JBT editor. It's empty file nothing to display in Web Browser
2. Open, edit and save file in JBT
3. Refresh file opened in Web Browser
ASSERT: File is properly displayed and aciidoc preview add-on works
4. Enable livereload add-on in Chrome
5. Update .asciidoc file in JBT
ERROR: File is not updated in Chrome
6. Reenable livereload add-on in chrome
ASSERT: File is refreshed
7. Open .asciidoc file in Chrome via file:/// protocol
ASSERT: Changes made to .asciidocfile via JBT are displayed in Chrome
ERROR: asciidoc preview add-on doesn't work for this file
> Support Asciidoctor files
> -------------------------
>
> Key: JBIDE-15506
> URL: https://issues.jboss.org/browse/JBIDE-15506
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Max Rydahl Andersen
> Labels: new_and_noteworthy
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
>
> Provide LiveReload support for Asciidoc (.adoc or .asciidoc) files in the browser.
> If the user has both LiveReload browser extension AND the new asciidoc.js preview extension (http://asciidoctor.org/news/2013/09/18/introducing-asciidoctor-js-live-pr...), then changes in a workspace file could (should) be previewed in the browser.
--
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, 6 months
[JBoss JIRA] (JBIDE-15612) install-grinder gets stuck after installing JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15612?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-15612:
-------------------------------
Description:
Seems that the prompt at the end of the installation of JBDS is not being caught and clicked by the install grinder, so the eclipse instance stays open forever (until the job times out).
Steps to reproduce locally:
{code}
# as root, install these if not already installed
yum install tigervnc.x86_64 tigervnc-server.x86_64 vinagre -y
exit
# in a terminal, run this:
vncserver
# then launch vinagre to connect to the VNC session:
vinagre localhost:1
# within the VNC session, run this:
git clone https://github.com/jbosstools/jbosstools-install-grinder/
cd jbosstools-install-grinder
mvn org.apache.maven.plugins:maven-dependency-plugin:2.7:unpack \
-Dartifact=org.jboss.tools.installation-tests:scripts:4.1.0.Beta1-SNAPSHOT:zip:delivery
cd scripts/target/scripts-*-delivery/
SCRIPTDIR=`pwd`
WORKSPACE=/tmp/jbtcentraltarget-verify
rm -fr ${WORKSPACE}; mkdir -p ${WORKSPACE}; cd ${WORKSPACE}
# must be lowercase kepler
eclipseBundleVersion=kepler.R
# or
eclipseBundleVersion=kepler.SR1
# path to where you store eclipse tar.gz files
eclipseCacheDirectory=${HOME}/tmp/Eclipse_Bundles
groovy ${SCRIPTDIR}/getAndInstallEclipse.groovy \
eclipseCacheDirectory=${eclipseCacheDirectory} \
eclipseBundleVersion=${eclipseBundleVersion}
INSTALL_PLAN="http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/;http:/..."
# or
INSTALL_PLAN="http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/;http:..."
groovy ${SCRIPTDIR}/testInstall.groovy ${WORKSPACE}/eclipse/ $INSTALL_PLAN
{code}
Here's a screenshot:
!install-grinder-gets-stuck.png!
was:
Seems that the prompt at the end of the installation of JBDS is not being caught and clicked by the install grinder, so the eclipse instance stays open forever (until the job times out).
Steps to reproduce locally:
{code}
# as root, install these if not already installed
yum install tigervnc.x86_64 tigervnc-server.x86_64 vinagre -y
exit
# in a terminal, run this:
vncserver
# then launch vinagre to connect to the VNC session:
vinagre localhost:1
# within the VNC session, run this:
git clone https://github.com/jbosstools/jbosstools-install-grinder/
cd jbosstools-install-grinder
mvn org.apache.maven.plugins:maven-dependency-plugin:2.7:unpack \
-Dartifact=org.jboss.tools.installation-tests:scripts:4.1.0.Beta1-SNAPSHOT:zip:delivery
cd scripts/target/scripts-*-delivery/
SCRIPTDIR=`pwd`
WORKSPACE=/tmp/jbtcentraltarget-verify
rm -fr ${WORKSPACE}; mkdir -p ${WORKSPACE}; cd ${WORKSPACE}
# must be lowercase kepler
eclipseBundleVersion=kepler.R
# or
eclipseBundleVersion=kepler.SR1
groovy ${SCRIPTDIR}/getAndInstallEclipse.groovy \
eclipseCacheDirectory=${HOME}/tmp/Eclipse_Bundles \
eclipseBundleVersion=${eclipseBundleVersion}
INSTALL_PLAN="http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/;http:/..."
# or
INSTALL_PLAN="http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/;http:..."
groovy ${SCRIPTDIR}/testInstall.groovy ${WORKSPACE}/eclipse/ $INSTALL_PLAN
{code}
Here's a screenshot:
!install-grinder-gets-stuck.png!
> install-grinder gets stuck after installing JBDS
> ------------------------------------------------
>
> Key: JBIDE-15612
> URL: https://issues.jboss.org/browse/JBIDE-15612
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa, testing-tools
> Affects Versions: 4.1.1.Alpha2
> Reporter: Nick Boldt
> Attachments: install-grinder-gets-stuck.png
>
>
> Seems that the prompt at the end of the installation of JBDS is not being caught and clicked by the install grinder, so the eclipse instance stays open forever (until the job times out).
> Steps to reproduce locally:
> {code}
> # as root, install these if not already installed
> yum install tigervnc.x86_64 tigervnc-server.x86_64 vinagre -y
> exit
> # in a terminal, run this:
> vncserver
> # then launch vinagre to connect to the VNC session:
> vinagre localhost:1
> # within the VNC session, run this:
> git clone https://github.com/jbosstools/jbosstools-install-grinder/
> cd jbosstools-install-grinder
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.7:unpack \
> -Dartifact=org.jboss.tools.installation-tests:scripts:4.1.0.Beta1-SNAPSHOT:zip:delivery
> cd scripts/target/scripts-*-delivery/
> SCRIPTDIR=`pwd`
> WORKSPACE=/tmp/jbtcentraltarget-verify
> rm -fr ${WORKSPACE}; mkdir -p ${WORKSPACE}; cd ${WORKSPACE}
> # must be lowercase kepler
> eclipseBundleVersion=kepler.R
> # or
> eclipseBundleVersion=kepler.SR1
> # path to where you store eclipse tar.gz files
> eclipseCacheDirectory=${HOME}/tmp/Eclipse_Bundles
> groovy ${SCRIPTDIR}/getAndInstallEclipse.groovy \
> eclipseCacheDirectory=${eclipseCacheDirectory} \
> eclipseBundleVersion=${eclipseBundleVersion}
> INSTALL_PLAN="http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/;http:/..."
> # or
> INSTALL_PLAN="http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/;http:..."
> groovy ${SCRIPTDIR}/testInstall.groovy ${WORKSPACE}/eclipse/ $INSTALL_PLAN
> {code}
> Here's a screenshot:
> !install-grinder-gets-stuck.png!
--
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, 6 months
[JBoss JIRA] (JBIDE-15612) install-grinder gets stuck after installing JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15612?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-15612:
-------------------------------
Description:
Seems that the prompt at the end of the installation of JBDS is not being caught and clicked by the install grinder, so the eclipse instance stays open forever (until the job times out).
Steps to reproduce locally:
{code}
# as root, install these if not already installed
yum install tigervnc.x86_64 tigervnc-server.x86_64 vinagre -y
exit
# in a terminal, run this:
vncserver
# then launch vinagre to connect to the VNC session:
vinagre localhost:1
# within the VNC session, run this:
git clone https://github.com/jbosstools/jbosstools-install-grinder/
cd jbosstools-install-grinder
mvn org.apache.maven.plugins:maven-dependency-plugin:2.7:unpack \
-Dartifact=org.jboss.tools.installation-tests:scripts:4.1.0.Beta1-SNAPSHOT:zip:delivery
cd scripts/target/scripts-*-delivery/
SCRIPTDIR=`pwd`
WORKSPACE=/tmp/jbtcentraltarget-verify
rm -fr ${WORKSPACE}; mkdir -p ${WORKSPACE}; cd ${WORKSPACE}
# must be lowercase kepler
eclipseBundleVersion=kepler.R
# or
eclipseBundleVersion=kepler.SR1
groovy ${SCRIPTDIR}/getAndInstallEclipse.groovy \
eclipseCacheDirectory=${HOME}/tmp/Eclipse_Bundles \
eclipseBundleVersion=${eclipseBundleVersion}
INSTALL_PLAN="http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/;http:/..."
# or
INSTALL_PLAN="http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/;http:..."
groovy ${SCRIPTDIR}/testInstall.groovy ${WORKSPACE}/eclipse/ $INSTALL_PLAN
{code}
Here's a screenshot:
!install-grinder-gets-stuck.png!
was:
Seems that the prompt at the end of the installation of JBDS is not being caught and clicked by the install grinder, so the eclipse instance stays open forever (until the job times out). Here's a screenshot:
> install-grinder gets stuck after installing JBDS
> ------------------------------------------------
>
> Key: JBIDE-15612
> URL: https://issues.jboss.org/browse/JBIDE-15612
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa, testing-tools
> Affects Versions: 4.1.1.Alpha2
> Reporter: Nick Boldt
> Attachments: install-grinder-gets-stuck.png
>
>
> Seems that the prompt at the end of the installation of JBDS is not being caught and clicked by the install grinder, so the eclipse instance stays open forever (until the job times out).
> Steps to reproduce locally:
> {code}
> # as root, install these if not already installed
> yum install tigervnc.x86_64 tigervnc-server.x86_64 vinagre -y
> exit
> # in a terminal, run this:
> vncserver
> # then launch vinagre to connect to the VNC session:
> vinagre localhost:1
> # within the VNC session, run this:
> git clone https://github.com/jbosstools/jbosstools-install-grinder/
> cd jbosstools-install-grinder
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.7:unpack \
> -Dartifact=org.jboss.tools.installation-tests:scripts:4.1.0.Beta1-SNAPSHOT:zip:delivery
> cd scripts/target/scripts-*-delivery/
> SCRIPTDIR=`pwd`
> WORKSPACE=/tmp/jbtcentraltarget-verify
> rm -fr ${WORKSPACE}; mkdir -p ${WORKSPACE}; cd ${WORKSPACE}
> # must be lowercase kepler
> eclipseBundleVersion=kepler.R
> # or
> eclipseBundleVersion=kepler.SR1
> groovy ${SCRIPTDIR}/getAndInstallEclipse.groovy \
> eclipseCacheDirectory=${HOME}/tmp/Eclipse_Bundles \
> eclipseBundleVersion=${eclipseBundleVersion}
> INSTALL_PLAN="http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/;http:/..."
> # or
> INSTALL_PLAN="http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/;http:..."
> groovy ${SCRIPTDIR}/testInstall.groovy ${WORKSPACE}/eclipse/ $INSTALL_PLAN
> {code}
> Here's a screenshot:
> !install-grinder-gets-stuck.png!
--
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, 6 months
[JBoss JIRA] (JBIDE-15612) install-grinder gets stuck after installing JBDS
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15612:
----------------------------------
Summary: install-grinder gets stuck after installing JBDS
Key: JBIDE-15612
URL: https://issues.jboss.org/browse/JBIDE-15612
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: qa, testing-tools
Affects Versions: 4.1.1.Alpha2
Reporter: Nick Boldt
Attachments: install-grinder-gets-stuck.png
Seems that the prompt at the end of the installation of JBDS is not being caught and clicked by the install grinder, so the eclipse instance stays open forever (until the job times out). Here's a screenshot:
--
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, 6 months