June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ] Misha Ali commented on JBIDE-20915: ----------------------------------- Added a line comment for a minor edit suggestion, but otherwise looks good to me. > HTML Page is not refreshed after page is changed in web browser with enabled LiveReload > --------------------------------------------------------------------------------------- > > Key: JBIDE-20915 > URL: https://issues.jboss.org/browse/JBIDE-20915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20150925-1252-B116 > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Labels: documentation > Fix For: 4.4.0.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Make some changes to opened page and save them. > ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser. > Repeat step 4. couple of times > ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3943) Wrong theme color in showlist menu

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBDS-3943?page=com.atlassian.jira.plugin.... ] Ondrej Dockal commented on JBDS-3943: ------------------------------------- Report created in bugzilla: Bug 495945. > Wrong theme color in showlist menu > ---------------------------------- > > Key: JBDS-3943 > URL: https://issues.jboss.org/browse/JBDS-3943 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.0.0.GA > Environment: Fedora 24, > devstudio: > Build id: GA-v20160603-1025-B5510, > Build date: 20160603-1025, > OpenJDK Runtime Environment (build 1.8.0_91-b14) > Reporter: Ondrej Dockal > Attachments: swtgtk3_0.png, swtgtk3_1.png > > > Show list menu of hidden tabs in editor appears to have wrong color theme. This changes with usage of webkitgtk lib, SWT_GTK3=0(1), used theme is default GTK. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3890) Devstudio installation takes a long, long time

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3890?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3890: -------------------------------- Fix Version/s: 10.0.1.Alpha1 > Devstudio installation takes a long, long time > ---------------------------------------------- > > Key: JBDS-3890 > URL: https://issues.jboss.org/browse/JBDS-3890 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.0.0.Alpha1 > Environment: Fedora 22 x64 > OpenJDK 1.8.0_91 > jboss-devstudio-10.0.0.Alpha1-v20160517-0518-B5370-installer-standalone.jar > Reporter: Jan Richter > Priority: Critical > Fix For: 10.0.1.Alpha1 > > Attachments: install.png, res.png > > > Some actual data here: > - Alpha1 (staged) build took 2:05 to install on my machine > - Alpha1 nightly (B5370) took 5:15 to install > Around the minute mark the installation just freezes in this state: > !install.png|thumbnail! > Meanwhile the trace says: > {noformat} > Committing the provisioning operation. > Operation completed in 275702 ms. > {noformat} > That is quite a long time it spent doing that operation. > Some jstack info can be found here: > http://pastebin.test.redhat.com/374700 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3903: -------------------------------- Component/s: (was: platform-installer) > Platform Installer does not Setup Docker Env-Vars > ------------------------------------------------- > > Key: JBDS-3903 > URL: https://issues.jboss.org/browse/JBDS-3903 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: docker > Affects Versions: 10.0.0.Alpha1 > Environment: Windows > Reporter: Thomas Mäder > Assignee: Denis Golovin > > I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection. > Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection. > As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3768) Installer - The installer should include quickstart options

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3768?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3768: -------------------------------- Fix Version/s: 10.0.1.Alpha1 > Installer - The installer should include quickstart options > ----------------------------------------------------------- > > Key: JBDS-3768 > URL: https://issues.jboss.org/browse/JBDS-3768 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Fix For: 10.0.1.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3642) Installer is too opaque - need a debug/verbose mode to track progress and debug failures

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3642?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3642: -------------------------------- Fix Version/s: 10.0.1.Alpha1 (was: 10.0.0.GA) > Installer is too opaque - need a debug/verbose mode to track progress and debug failures > ---------------------------------------------------------------------------------------- > > Key: JBDS-3642 > URL: https://issues.jboss.org/browse/JBDS-3642 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.1.Alpha1 > > > The install.log created by the installer does not contain a detailed listing of all actions performed by the installer. Setting the install browser into a debug mode ( "set PDKI_DEBUG=true" ) generated additional information, but it is still node a detailed dump of all actions. Can we add a debug/verbose/trace mode? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3868) Document (and check) required disk space before beginning install

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3868?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3868: ----------------------------- Target Release: (was: ) > Document (and check) required disk space before beginning install > ----------------------------------------------------------------- > > Key: JBDS-3868 > URL: https://issues.jboss.org/browse/JBDS-3868 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Windows 7/64 bit > Reporter: Robert Terzi > Priority: Minor > Fix For: 10.0.1.Alpha1 > > > The installer and it's documentation should indicate the minimum required disk space before beginning the download and installation process. > Between temporary files, and download/installs going on in parallel. I'm guessing at least 10-15 GB free is needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3868) Document (and check) required disk space before beginning install

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3868?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3868: -------------------------------- Fix Version/s: 10.0.1.Alpha1 (was: 10.0.0.GA) > Document (and check) required disk space before beginning install > ----------------------------------------------------------------- > > Key: JBDS-3868 > URL: https://issues.jboss.org/browse/JBDS-3868 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Windows 7/64 bit > Reporter: Robert Terzi > Priority: Minor > Fix For: 10.0.1.Alpha1 > > > The installer and it's documentation should indicate the minimum required disk space before beginning the download and installation process. > Between temporary files, and download/installs going on in parallel. I'm guessing at least 10-15 GB free is needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3758) when something goes wrong, give user call to action / report of what went wrong

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3758?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3758: -------------------------------- Fix Version/s: 10.0.1.Alpha1 (was: 10.0.0.GA) > when something goes wrong, give user call to action / report of what went wrong > ------------------------------------------------------------------------------- > > Key: JBDS-3758 > URL: https://issues.jboss.org/browse/JBDS-3758 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Nick Boldt > Fix For: 10.0.1.Alpha1 > > Attachments: jbds-install-ste-failed-progress-bar-keeps-moving.png > > > I attempted to install from Setup-bundled-0.0.2-20160401-33.exe and while the installer was OK with my using my pre-installed JDK 8 in C:\Program Files\Java\jdk1.8.0_25 (or C:\Program Files\Java\jre1.8.0_25) it then ran into a problem using that JDK to install JBDS. > I noticed the problem at about 12% on the progress bar but it was still moving along at 45% when I grabbed the screenshot (attached). > If a failure occurs, perhaps *we could change the bar from blue to red and move it to 100%* ? > Also, should there be a call to action for the user? > Even something simple like "*go check in C:\DeveloperPlatform\install.log for what might have happened*" would be useful here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3863) Platform Installer Hung after CDK install failed, no way to cancel, no info on error.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3863?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3863: -------------------------------- Fix Version/s: 10.0.1.Alpha1 (was: 10.0.0.GA) > Platform Installer Hung after CDK install failed, no way to cancel, no info on error. > -------------------------------------------------------------------------------------- > > Key: JBDS-3863 > URL: https://issues.jboss.org/browse/JBDS-3863 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Windows 7/64 bit. > (Some components of previous manual CDK install on the system). > Reporter: Robert Terzi > Assignee: Denis Golovin > Fix For: 10.0.1.Alpha1 > > Attachments: jbds-install-log-win7-error.txt > > > Using the platform installer, CDK installation failed, progress shown as 99%. At this point the installer was hung. > Note: > * CDK install progress said Failed, with progress stuck at 99%. > * There is no way to cancel out of the install. > * There was no pop-up about error messages. > * No indication of where to look for error messages/logs etc.was provided. > * CDK was previously installed manually. However, the installer window didn't say a previous CDK installation was detected, but the log does show it deleted the previous cdkv2 box. > From the log it looks like the box add command failed. This might have been due to disk space, but it's not clear/obvious from the log. > Note: after killing the installer and trying the `vagrant box add` command copied from the log file manually in Cygwin bash the box add command succeeded. The test system had 5-15 GB of free space between the installation started. > Full log attached, excerpt here. > Tue, 26 Apr 2016 18:05:38 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\rhel-vagrant-virtualbox.box to c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\rhel-vagrant-virtualbox.box to c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\pscp.exe to c:\sw\rhjbds\cdk\bin\pscp.exe > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\pscp.exe to c:\sw\rhjbds\cdk\bin\pscp.exe SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write c:\sw\rhjbds\cdk\components\rhel\rhel-ose\.cdk > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write c:\sw\rhjbds\cdk\components\rhel\rhel-ose\.cdk SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Execute powershell -ExecutionPolicy,ByPass,-File,C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - Execute powershell -ExecutionPolicy,ByPass,-File,C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 SUCCESS > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - postVagrantSetup called > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - Execute command vagrant plugin install "c:\sw\rhjbds\cdk\plugins\vagrant-registration-1.2.1.gem" > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - Execute options { > "env": { > "path": "C:\\HashiCorp\\Vagrant\\bin;C:\\Program Files\\Oracle\\VirtualBox\\;" > } > } > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Installing the 'c:\sw\rhjbds\cdk\plugins\vagrant-registration-1.2.1.gem' plugin. This can take a few minutes... > Installed the plugin 'vagrant-registration (1.2.1)'! > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Execute vagrant plugin install "c:\sw\rhjbds\cdk\plugins\vagrant-registration-1.2.1.gem" SUCCESS > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Execute command vagrant box remove cdkv2 -f > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Execute options { > "env": { > "path": "C:\\HashiCorp\\Vagrant\\bin;C:\\Program Files\\Oracle\\VirtualBox\\;" > } > } > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Removing box 'cdkv2' (v0) with provider 'virtualbox'... > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Execute vagrant box remove cdkv2 -f SUCCESS > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Execute command vagrant box add --name cdkv2 "c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box" > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Execute options { > "env": { > "path": "C:\\HashiCorp\\Vagrant\\bin;C:\\Program Files\\Oracle\\VirtualBox\\;" > } > } > Tue, 26 Apr 2016 18:06:10 GMT-ERROR: cdk - Error: Command failed: vagrant box add --name cdkv2 "c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box" > The box failed to unpackage properly. Please verify that the box > file you're trying to add is not corrupted and try again. The > output from attempting to unpackage (if any): > x box.ovf > x Vagrantfile > x vagrant-virtualbox-box.vmdk: Write failed > x metadata.json > bsdtar.EXE: Error exit delayed from previous errors. > Tue, 26 Apr 2016 18:06:10 GMT-ERROR: cdk - The box failed to unpackage properly. Please verify that the box > file you're trying to add is not corrupted and try again. The > output from attempting to unpackage (if any): > x box.ovf > x Vagrantfile > x vagrant-virtualbox-box.vmdk: Write failed > x metadata.json > bsdtar.EXE: Error exit delayed from previous errors. > Tue, 26 Apr 2016 18:06:10 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant box add --name cdkv2 "c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box" > The box failed to unpackage properly. Please verify that the box > file you're trying to add is not corrupted and try again. The > output from attempting to unpackage (if any): > x box.ovf > x Vagrantfile > x vagrant-virtualbox-box.vmdk: Write failed > x metadata.json > bsdtar.EXE: Error exit delayed from previous errors. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016