November 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4168) Updated the "Setting up CDK software components" for adding Vagrant box

by Budh Ram Gurung (JIRA)

[ https://issues.jboss.org/browse/JBDS-4168?page=com.atlassian.jira.plugin.... ] Budh Ram Gurung updated JBDS-4168: ---------------------------------- Component/s: documentation > Updated the "Setting up CDK software components" for adding Vagrant box > ----------------------------------------------------------------------- > > Key: JBDS-4168 > URL: https://issues.jboss.org/browse/JBDS-4168 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: cdk, documentation > Reporter: Budh Ram Gurung > > We have updated our Vagrantfiles so that user can use any customized box name. > This can be easily done with adding an environment variable like *BOX*. > The PR is sent upstream [here|https://github.com/projectatomic/adb-atomic-developer-bundle/pull/569]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4153) Cannot install Fuse Runtime on Windows using the installer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBDS-4153?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBDS-4153: ---------------------------------- Thanks guys - [~apodhrad] - could I impose on you one more time to check the skinny installer - just to make sure it's okay on windows? http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... Thanks!! > Cannot install Fuse Runtime on Windows using the installer > ---------------------------------------------------------- > > Key: JBDS-4153 > URL: https://issues.jboss.org/browse/JBDS-4153 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Priority: Blocker > Fix For: 10.x > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > > On Windows, if using the installer with the Fuse Runtime and keeping it checked, the installation fails. > i used https://devstudio.redhat.com/10.0/staging/updates/integration-stack/10.0.... > !screenshot-1.png|thumbnail! > !screenshot-2.png|thumbnail! > !screenshot-3.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-900) Skip more drools tests when jira describing issue is not fixed

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-900?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky edited comment on JBTIS-900 at 11/8/16 7:16 AM: ------------------------------------------------------------------ [~tomasdavidorg] what's the difference between this issue and JBTIS-755 ? was (Author: apodhrad): [~tomasdavidorg] what's the difference between this issues and JBTIS-755 ? > Skip more drools tests when jira describing issue is not fixed > -------------------------------------------------------------- > > Key: JBTIS-900 > URL: https://issues.jboss.org/browse/JBTIS-900 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: drools/ jBPM, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Tomas David > Assignee: Tomas David > Priority: Minor > Fix For: 4.4.0.Final > > > Use the mechanism for skipping test when jira describing issue is not fixed for improve stability of drools test suite. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-900) Skip more drools tests when jira describing issue is not fixed

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-900?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-900: ----------------------------------------- [~tomasdavidorg] what's the difference between this issues and JBTIS-755 ? > Skip more drools tests when jira describing issue is not fixed > -------------------------------------------------------------- > > Key: JBTIS-900 > URL: https://issues.jboss.org/browse/JBTIS-900 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: drools/ jBPM, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Tomas David > Assignee: Tomas David > Priority: Minor > Fix For: 4.4.0.Final > > > Use the mechanism for skipping test when jira describing issue is not fixed for improve stability of drools test suite. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4161) VAGRANT_HOME is not used and thus the vagrant plugin installation is failing

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4161?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4161. ----------------------------- Everything seems to be working again in build 217. > VAGRANT_HOME is not used and thus the vagrant plugin installation is failing > ---------------------------------------------------------------------------- > > Key: JBDS-4161 > URL: https://issues.jboss.org/browse/JBDS-4161 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM3 > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: install.log > > > see plugin install failure and VAGRANT_HOME well defined > {noformat} > Fri, 04 Nov 2016 08:20:43 GMT-INFO: cdk - Execute command vagrant plugin install "c:\install\DevelopmentSuite-1.2-try2\cdk\plugins\landrush-1.2.0.dev.gem" > Fri, 04 Nov 2016 08:20:49 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install "c:\install\DevelopmentSuite-1.2-try2\cdk\plugins\landrush-1.2.0.dev.gem" > [0;31mThe directory where plugins are installed (the Vagrant home directory) > has a space in it. On Windows, there is a bug in Ruby when compiling > plugins into directories with spaces. Please move your Vagrant home > directory to a path without spaces and try again.[0m > Fri, 04 Nov 2016 08:20:49 GMT-ERROR: cdk - [0;31mThe directory where plugins are installed (the Vagrant home directory) > has a space in it. On Windows, there is a bug in Ruby when compiling > plugins into directories with spaces. Please move your Vagrant home > directory to a path without spaces and try again.[0m > Fri, 04 Nov 2016 08:20:49 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant plugin install "c:\install\DevelopmentSuite-1.2-try2\cdk\plugins\landrush-1.2.0.dev.gem" > [0;31mThe directory where plugins are installed (the Vagrant home directory) > has a space in it. On Windows, there is a bug in Ruby when compiling > plugins into directories with spaces. Please move your Vagrant home > directory to a path without spaces and try again.[0m > Fri, 04 Nov 2016 08:28:34 GMT-INFO: Download finished for: jbds > Fri, 04 Nov 2016 08:28:34 GMT-INFO: Install started for: jbds > Fri, 04 Nov 2016 08:28:34 GMT-INFO: jbds - Generate devstudio auto install file content > Fri, 04 Nov 2016 08:28:34 GMT-INFO: jbds - Generate devstudio auto install file content SUCCESS > Fri, 04 Nov 2016 08:28:34 GMT-INFO: jbds - Write C:\Users\AURELI~1\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 04 Nov 2016 08:28:34 GMT-INFO: jbds - Write C:\Users\AURELI~1\AppData\Local\Temp\jbds-autoinstall.xml SUCCESS > Fri, 04 Nov 2016 08:28:34 GMT-INFO: jbds - headlessInstall() called > Fri, 04 Nov 2016 08:28:34 GMT-INFO: jbds - Execute C:\Program Files\Java\jre1.8.0_102\bin\java -DTRACE=true,-jar,C:\Users\AURELI~1\AppData\Local\Temp\jbds.jar,C:\Users\AURELI~1\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 04 Nov 2016 08:31:39 GMT-INFO: jbds - TRACE enabled. > executeCommand > params: cmd.exe > params: /C > params: set > stdout: > ALLUSERSPROFILE=C:\ProgramData > APPDATA=C:\Users\Aurelien Pupier\AppData\Roaming > CHE_VERSION=nightly > CommonProgramFiles=C:\Program Files\Common Files > CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files > CommonProgramW6432=C:\Program Files\Common Files > COMPUTERNAME=DESKTOP-9NT300B > ComSpec=C:\WINDOWS\system32\cmd.exe > DOCKER_CERT_PATH-bak=C:\certificate > DOCKER_HOST-back=tcp://10.1.2.2:2376 > DOCKER_MACHINE_NAME-bak=498b304 > DOCKER_TLS_VERIFY-bak=1 > DOCKER_TOOLBOX_INSTALL_PATH-bak=C:\Program Files\Docker Toolbox > DOCKER_VM_IP=10.0.75.2/24 > GIT_HOME=C:\Program Files\Git > GOOGLE_API_KEY=AIzaSyAQfxPJiounkhOjODEO5ZieffeBv6yft2Q > HOMEDRIVE=C: > HOMEPATH=\Users\Aurelien Pupier > JAVA_HOME=C:\Program Files\Java\jdk1.8.0_65 > LOCALAPPDATA=C:\Users\Aurelien Pupier\AppData\Local > LOGONSERVER=\\DESKTOP-9NT300B > MAVEN_HOME=C:\install\apache-maven-3.3.9-bin\apache-maven-3.3.9 > NUMBER_OF_PROCESSORS=8 > OS=Windows_NT > Path=C:\Program Files\Docker\Docker\Resources\bin;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Skype\Phone\;C:\Program Files (x86)\PuTTY\;C:\Program Files\RedHat\java-1.8.0-openjdk-1.8.0.102-1\bin;C:\HashiCorp\Vagrant\bin;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;c:\install\DevelopmentSuite-1.2-try1\cdk\bin;c:\install\DevelopmentSuite-1.1.0-try4\cdk\bin;c:\install\DevelopmentSuite-1.1.0-try2\cdk\bin;c:\install\DevelopmentSuite-1.1.0-try2\cdk\bin;c:\install\DevelopmentSuite-1.1.0\cdk\bin;c:\install\DevelopmentSuite\cdk\bin;c:\install\DevelopmentSuite\cygwin\bin;C:\OpenShift;C:\Program Files\Docker Toolbox;C:\install\apache-maven-3.3.9-bin\apache-maven-3.3.9\bin;C:\Program Files\Git\bin;C:\Users\Aurelien Pupier\AppData\Local\Microsoft\WindowsApps;C:\install\che > PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC > PROCESSOR_ARCHITECTURE=AMD64 > PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 60 Stepping 3, GenuineIntel > PROCESSOR_LEVEL=6 > PROCESSOR_REVISION=3c03 > ProgramData=C:\ProgramData > ProgramFiles=C:\Program Files > ProgramFiles(x86)=C:\Program Files (x86) > ProgramW6432=C:\Program Files > PROMPT=$P$G > PSModulePath=C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules > PUBLIC=C:\Users\Public > SystemDrive=C: > SystemRoot=C:\WINDOWS > TEMP=C:\Users\AURELI~1\AppData\Local\Temp > TMP=C:\Users\AURELI~1\AppData\Local\Temp > USERDOMAIN=DESKTOP-9NT300B > USERDOMAIN_ROAMINGPROFILE=DESKTOP-9NT300B > USERNAME=Aurelien Pupier > USERPROFILE=C:\Users\Aurelien Pupier > VAGRANT_DETECTED_OS=cygwin > VAGRANT_HOME=C:\install\.vagrant_home > VBOX_MSI_INSTALL_PATH=C:\Program Files\Oracle\VirtualBox\ > windir=C:\WINDOWS > __COMPAT_LAYER=DetectorsWin7 Installer > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15155) LiveReload is not working with internal Web Browser

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15155?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-15155. ------------------------------------ Verified in devstudio 10.2.0.AM3-v20161104-1659-B6372 on RHEL7, Windows 8.1, Windows 10, latest Fedora, Mac > LiveReload is not working with internal Web Browser > --------------------------------------------------- > > Key: JBIDE-15155 > URL: https://issues.jboss.org/browse/JBIDE-15155 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.CR1 > Reporter: Rastislav Wagner > Assignee: Xavier Coulon > Fix For: 4.4.2.AM3 > > > 1. Import HTML5 project from JBoss Central and run it on Server > 2. Click on Show In > Web Browser via LiveReload Server on HTML 5 project within Server View > ASSERT: http://localhost:8080/jboss-as-kitchensink-html5-mobile/ page is opened either in default web browser and internal eclipse browser > 3. Change index.html file of HTML5 project and save changes > ASSERT: Page is reloaded in default web browser > ERROR: Page is not reloaded in internal eclipse browser -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15155) LiveReload is not working with internal Web Browser

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15155?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-15155: ------------------------------------------ [~xcoulon] I tried this on Windows 8.1, Windows 10, Mac, Rhel7 and latest Fedora and it worked everywhere. So i will mark this as resolved & close it > LiveReload is not working with internal Web Browser > --------------------------------------------------- > > Key: JBIDE-15155 > URL: https://issues.jboss.org/browse/JBIDE-15155 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.CR1 > Reporter: Rastislav Wagner > Assignee: Xavier Coulon > Fix For: 4.4.2.AM3 > > > 1. Import HTML5 project from JBoss Central and run it on Server > 2. Click on Show In > Web Browser via LiveReload Server on HTML 5 project within Server View > ASSERT: http://localhost:8080/jboss-as-kitchensink-html5-mobile/ page is opened either in default web browser and internal eclipse browser > 3. Change index.html file of HTML5 project and save changes > ASSERT: Page is reloaded in default web browser > ERROR: Page is not reloaded in internal eclipse browser -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15155) LiveReload is not working with internal Web Browser

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15155?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-15155: ------------------------------------- Fix Version/s: 4.4.2.AM3 (was: LATER) > LiveReload is not working with internal Web Browser > --------------------------------------------------- > > Key: JBIDE-15155 > URL: https://issues.jboss.org/browse/JBIDE-15155 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.CR1 > Reporter: Rastislav Wagner > Assignee: Xavier Coulon > Fix For: 4.4.2.AM3 > > > 1. Import HTML5 project from JBoss Central and run it on Server > 2. Click on Show In > Web Browser via LiveReload Server on HTML 5 project within Server View > ASSERT: http://localhost:8080/jboss-as-kitchensink-html5-mobile/ page is opened either in default web browser and internal eclipse browser > 3. Change index.html file of HTML5 project and save changes > ASSERT: Page is reloaded in default web browser > ERROR: Page is not reloaded in internal eclipse browser -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4159) On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not

by Aileen Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBDS-4159?page=com.atlassian.jira.plugin.... ] Aileen Cunningham commented on JBDS-4159: ----------------------------------------- The first 2 options seem better as the user may not know in advance if he needs vbox or hyper-v. Can we do both online version and the big bundle installer so that the user has a choice whether to download huge file? > On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-4159 > URL: https://issues.jboss.org/browse/JBDS-4159 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 1.1.0.GA > Reporter: Aurélien Pupier > Priority: Blocker > > On windows, the latest version of Docker is using Hyper-V and no more VirtualBox. The current embedded CDK is expecting Docker in a Virtualbox. The installer should handle both cases. > here is the error: > {noformat} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > ==> default: Matching MAC address for NAT networking... > ==> default: Setting the name of the VM: rhel-ose_default_1478167717348_52569 > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > There was an error while executing `VBoxManage`, a CLI used by Vagrant > for controlling VirtualBox. The command and stderr is shown below. > Command: ["startvm", "27ab7252-7971-4276-abec-1aba54965c62", "--type", "headless"] > Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX) > VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4168) Updated the "Setting up CDK software components" for adding Vagrant box

by Budh Ram Gurung (JIRA)

[ https://issues.jboss.org/browse/JBDS-4168?page=com.atlassian.jira.plugin.... ] Budh Ram Gurung updated JBDS-4168: ---------------------------------- Description: We have updated our Vagrantfiles so that user can use any customized box name. This can be easily done with adding an environment variable like **BOX**. The PR is sent upstream [here|https://github.com/projectatomic/adb-atomic-developer-bundle/pull/569]. was: We have updated our Vagrantfiles so that user can use any customized box name. This can be easily done with adding an environment variable like `BOX`. The PR is sent upstream [here|https://github.com/projectatomic/adb-atomic-developer-bundle/pull/569]. > Updated the "Setting up CDK software components" for adding Vagrant box > ----------------------------------------------------------------------- > > Key: JBDS-4168 > URL: https://issues.jboss.org/browse/JBDS-4168 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: cdk > Reporter: Budh Ram Gurung > > We have updated our Vagrantfiles so that user can use any customized box name. > This can be easily done with adding an environment variable like **BOX**. > The PR is sent upstream [here|https://github.com/projectatomic/adb-atomic-developer-bundle/pull/569]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 November 2016