September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4036) Installer should check Virtualbox installed is from 5.0.x sream

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4036?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4036: -------------------------------- Fix Version/s: 10.1.0.GA > Installer should check Virtualbox installed is from 5.0.x sream > --------------------------------------------------------------- > > Key: JBDS-4036 > URL: https://issues.jboss.org/browse/JBDS-4036 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > > Vagrant 1.8.1 does not recognize 5.1.x and starts to download 5.0.x on first vagrant up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15189) Check compatible JRE/JDK when adding server via runtime detection

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15189?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-15189. ------------------------------ Verified in Devstudio 10.1.0.GA-v20160901-0633-B5917 > Check compatible JRE/JDK when adding server via runtime detection > ----------------------------------------------------------------- > > Key: JBIDE-15189 > URL: https://issues.jboss.org/browse/JBIDE-15189 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.1.0.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.4.1.AM3 > > > Now, people are not allowed to create runtime when no compatible java is configured in eclipse (JBIDE-14858). > But when adding server and runtime via runtime detection, server and runtime are added even though no compatible java is configured. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4033) Cannot add virtualbox box files on windows during installation of CDK via devstuite bundle installer

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBDS-4033?page=com.atlassian.jira.plugin.... ] Ondrej Dockal updated JBDS-4033: -------------------------------- Workaround Description: Install Microsoft visual C++ 2010 library. Adding of virtualbox.box is functional. I tested manual adding after installation of library, so far. When library is installed, devsuite installation process ends up with status completed for all components. was:Install Microsoft visual C++ 2010 library. Adding of virtualbox.box is functional. I tested manual adding after installation of library, so far. > Cannot add virtualbox box files on windows during installation of CDK via devstuite bundle installer > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-4033 > URL: https://issues.jboss.org/browse/JBDS-4033 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 1.1.0.GA > Environment: NB: windows 10 Pro, x86_64 > Virtual machines: > windows 10 Enterprise, x86_64 > windows 7 Pro, x86_64, SP1 > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Priority: Critical > > Installation ends up with CDK failed status. Others installation of components is completed. > Error message from install log: > ------------------------------ > Wed, 31 Aug 2016 11:23:37 GMT-INFO: cdk - Execute command vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box > Wed, 31 Aug 2016 11:23:37 GMT-INFO: cdk - Execute options { > "env": { > "ALLUSERSPROFILE": "C:\\ProgramData", > "APPDATA": "C:\\Users\\jbossqa\\AppData\\Roaming", > "CommonProgramFiles": "C:\\Program Files\\Common Files", > "CommonProgramFiles(x86)": "C:\\Program Files (x86)\\Common Files", > "CommonProgramW6432": "C:\\Program Files\\Common Files", > "COMPUTERNAME": "SOME-PC", > "ComSpec": "C:\\Windows\\system32\\cmd.exe", > "FP_NO_HOST_CHECK": "NO", > "GOOGLE_API_KEY": "AIzaSyAQfxPJiounkhOjODEO5ZieffeBv6yft2Q", > "HOMEDRIVE": "C:", > "HOMEPATH": "\\Users\\jbossqa", > "LOCALAPPDATA": "C:\\Users\\jbossqa\\AppData\\Local", > "LOGONSERVER": "\\\\SOME-PC", > "NUMBER_OF_PROCESSORS": "2", > "OS": "Windows_NT", > "Path": "C:\\Windows\\system32;C:\\Windows;C:\\Windows\\System32\\Wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\;C:\\DevelopmentSuite\\jdk8\\bin;C:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;C:\\DevelopmentSuite\\vagrant\\bin;bin;C:\\DevelopmentSuite\\virtualbox\\", > "PATHEXT": ".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC", > "PROCESSOR_ARCHITECTURE": "AMD64", > "PROCESSOR_IDENTIFIER": "Intel64 Family 6 Model 60 Stepping 1, GenuineIntel", > "PROCESSOR_LEVEL": "6", > "PROCESSOR_REVISION": "3c01", > "ProgramData": "C:\\ProgramData", > "ProgramFiles": "C:\\Program Files", > "ProgramFiles(x86)": "C:\\Program Files (x86)", > "ProgramW6432": "C:\\Program Files", > "PSModulePath": "C:\\Windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\", > "PUBLIC": "C:\\Users\\Public", > "SystemDrive": "C:", > "SystemRoot": "C:\\Windows", > "TEMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp", > "TMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp", > "USERDOMAIN": "Some-PC", > "USERNAME": "jbossqa", > "USERPROFILE": "C:\\Users\\jbossqa", > "VAGRANT_DETECTED_OS": "cygwin", > "VBOX_MSI_INSTALL_PATH": "C:\\DevelopmentSuite\\virtualbox\\", > "windir": "C:\\Windows", > "windows_tracing_flags": "3", > "windows_tracing_logfile": "C:\\BVTBin\\Tests\\installpackage\\csilogfile.log", > "__COMPAT_LAYER": "VistaSetup" > }, > "cwd": "c:\\DevelopmentSuite\\cdk\\boxes" > } > Wed, 31 Aug 2016 11:23:39 GMT-ERROR: cdk - Error: Command failed: vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box > [0;31mAn error occurred while downloading the remote file. The error > message, if any, is reproduced below. Please fix this error and try > again. > ---------------------- > After manual attempt to add box via cli with commad: vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box: > --------------------- > C:\DevelopmentSuite\cdk\boxes>vagrant box add --name cdkv2 rhel-vagrant-virtualb > ox.box > ==> box: Box file was not detected as metadata. Adding it directly... > ==> box: Adding box 'cdkv2' (v0) for provider: > box: Unpacking necessary files from: file://C:/DevelopmentSuite/cdk/boxes/rh > el-vagrant-virtualbox.box > box: > An error occurred while downloading the remote file. The error > message, if any, is reproduced below. Please fix this error and try > again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4036) Installer should check Virtualbox installed is from 5.0.x sream

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-4036?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-4036: ----------------------------- > Installer should check Virtualbox installed is from 5.0.x sream > --------------------------------------------------------------- > > Key: JBDS-4036 > URL: https://issues.jboss.org/browse/JBDS-4036 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > > Vagrant 1.8.1 does not recognize 5.1.x and starts to download 5.0.x on first vagrant up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4036) Installer should check Virtualbox installed is from 5.0.x sream

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4036: ----------------------------------- Summary: Installer should check Virtualbox installed is from 5.0.x sream Key: JBDS-4036 URL: https://issues.jboss.org/browse/JBDS-4036 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.1.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Vagrant 1.8.1 does not recognize 5.1.x and starts to download 5.0.x on first vagrant up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4033) Cannot add virtualbox box files on windows during installation of CDK via devstuite bundle installer

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBDS-4033?page=com.atlassian.jira.plugin.... ] Ondrej Dockal updated JBDS-4033: -------------------------------- Summary: Cannot add virtualbox box files on windows during installation of CDK via devstuite bundle installer (was: Cannot add virtualbox box files on windows duringinstallation CDK via devstuite bundle installer) > Cannot add virtualbox box files on windows during installation of CDK via devstuite bundle installer > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-4033 > URL: https://issues.jboss.org/browse/JBDS-4033 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 1.1.0.GA > Environment: NB: windows 10 Pro, x86_64 > Virtual machines: > windows 10 Enterprise, x86_64 > windows 7 Pro, x86_64, SP1 > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Priority: Critical > > Installation ends up with CDK failed status. Others installation of components is completed. > Error message from install log: > ------------------------------ > Wed, 31 Aug 2016 11:23:37 GMT-INFO: cdk - Execute command vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box > Wed, 31 Aug 2016 11:23:37 GMT-INFO: cdk - Execute options { > "env": { > "ALLUSERSPROFILE": "C:\\ProgramData", > "APPDATA": "C:\\Users\\jbossqa\\AppData\\Roaming", > "CommonProgramFiles": "C:\\Program Files\\Common Files", > "CommonProgramFiles(x86)": "C:\\Program Files (x86)\\Common Files", > "CommonProgramW6432": "C:\\Program Files\\Common Files", > "COMPUTERNAME": "SOME-PC", > "ComSpec": "C:\\Windows\\system32\\cmd.exe", > "FP_NO_HOST_CHECK": "NO", > "GOOGLE_API_KEY": "AIzaSyAQfxPJiounkhOjODEO5ZieffeBv6yft2Q", > "HOMEDRIVE": "C:", > "HOMEPATH": "\\Users\\jbossqa", > "LOCALAPPDATA": "C:\\Users\\jbossqa\\AppData\\Local", > "LOGONSERVER": "\\\\SOME-PC", > "NUMBER_OF_PROCESSORS": "2", > "OS": "Windows_NT", > "Path": "C:\\Windows\\system32;C:\\Windows;C:\\Windows\\System32\\Wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\;C:\\DevelopmentSuite\\jdk8\\bin;C:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;C:\\DevelopmentSuite\\vagrant\\bin;bin;C:\\DevelopmentSuite\\virtualbox\\", > "PATHEXT": ".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC", > "PROCESSOR_ARCHITECTURE": "AMD64", > "PROCESSOR_IDENTIFIER": "Intel64 Family 6 Model 60 Stepping 1, GenuineIntel", > "PROCESSOR_LEVEL": "6", > "PROCESSOR_REVISION": "3c01", > "ProgramData": "C:\\ProgramData", > "ProgramFiles": "C:\\Program Files", > "ProgramFiles(x86)": "C:\\Program Files (x86)", > "ProgramW6432": "C:\\Program Files", > "PSModulePath": "C:\\Windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\", > "PUBLIC": "C:\\Users\\Public", > "SystemDrive": "C:", > "SystemRoot": "C:\\Windows", > "TEMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp", > "TMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp", > "USERDOMAIN": "Some-PC", > "USERNAME": "jbossqa", > "USERPROFILE": "C:\\Users\\jbossqa", > "VAGRANT_DETECTED_OS": "cygwin", > "VBOX_MSI_INSTALL_PATH": "C:\\DevelopmentSuite\\virtualbox\\", > "windir": "C:\\Windows", > "windows_tracing_flags": "3", > "windows_tracing_logfile": "C:\\BVTBin\\Tests\\installpackage\\csilogfile.log", > "__COMPAT_LAYER": "VistaSetup" > }, > "cwd": "c:\\DevelopmentSuite\\cdk\\boxes" > } > Wed, 31 Aug 2016 11:23:39 GMT-ERROR: cdk - Error: Command failed: vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box > [0;31mAn error occurred while downloading the remote file. The error > message, if any, is reproduced below. Please fix this error and try > again. > ---------------------- > After manual attempt to add box via cli with commad: vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box: > --------------------- > C:\DevelopmentSuite\cdk\boxes>vagrant box add --name cdkv2 rhel-vagrant-virtualb > ox.box > ==> box: Box file was not detected as metadata. Adding it directly... > ==> box: Adding box 'cdkv2' (v0) for provider: > box: Unpacking necessary files from: file://C:/DevelopmentSuite/cdk/boxes/rh > el-vagrant-virtualbox.box > box: > An error occurred while downloading the remote file. The error > message, if any, is reproduced below. Please fix this error and try > again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4035) Missing uninstall.ps1 script

by Lukáš Valach (JIRA)

Lukáš Valach created JBDS-4035: ---------------------------------- Summary: Missing uninstall.ps1 script Key: JBDS-4035 URL: https://issues.jboss.org/browse/JBDS-4035 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.1.0.AM3 Environment: Windows 7 Reporter: Lukáš Valach Priority: Minor Platform installer doesn't copies the uninstall.ps1 script to the TARGET_FOLTER/uninstall/ directory when the target folder already exists. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-408) Properties do not show information about selected image/container in respective tab [EBZ#500638]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-408: --------------------------------------- Summary: Properties do not show information about selected image/container in respective tab [EBZ#500638] Key: ERT-408 URL: https://issues.jboss.org/browse/ERT-408 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Properties view is empty if an image or a container is selected in Docker Images or Docker Containers tab. This was working in previous versions. When an image or a container is selected in Docker Explorer, properties view shows correct information. Eclipse version: Neon Release (4.6.0) Build id: 20160613-1800 Docker Tooling: 2.1.0.201608292220 Docker version: Docker version 1.12.1, build 23cf638 (from upstream repository) Tested on Fedora 24 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3980) Staging update site advertises old latest build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3980?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3980: ---------------------------------- s/10.0.0.GA-b/10.0.1.AM2 > Staging update site advertises old latest build > ----------------------------------------------- > > Key: JBDS-3980 > URL: https://issues.jboss.org/browse/JBDS-3980 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Minor > Fix For: 10.1.0.AM2 > > > Staging updatesite > https://devstudio.redhat.com/10.0/staging/updates/ > still shows 10.0.0.GA-b as latest build. It's just this string that is outdated, the build itself is up to date. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3986) support building devstudio on windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3986?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-3986. ------------------------------- Resolution: Done Fix build errors when running on windows > support building devstudio on windows > ------------------------------------- > > Key: JBDS-3986 > URL: https://issues.jboss.org/browse/JBDS-3986 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 10.1.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.x > > > Support building devstudio on windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 September 2016