September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-22990) OpenShift New and Noteworthy for 4.4.1.AM3

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22990?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22990. --------------------------------- Verified and N&N is documented. Looks good to me. Closing. > OpenShift New and Noteworthy for 4.4.1.AM3 > ------------------------------------------ > > Key: JBIDE-22990 > URL: https://issues.jboss.org/browse/JBIDE-22990 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.4.1.AM3 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If OpenShift is not listed here check if there are issues that should be added and add them. > Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23054) Build for java-language-server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23054?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23054: ------------------------------------ How often will this be published? Do you have a preferred timestamp format? Should automated cleanup ever happen? Is this stuff specific to a version of Eclipse? Do you plan to differentiate between /stable/ (GA) or /development/ (milestone) releases? What about snapshots (CI)? > Build for java-language-server > ------------------------------ > > Key: JBIDE-23054 > URL: https://issues.jboss.org/browse/JBIDE-23054 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Gorkem Ercan > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > I need a build job that can build java-language server and publish it to download server for the use of VSCode extension. > Sources:_ https://github.com/gorkem/java-language-server_ > Build command: _mvn -Pserver-distro clean verify_ > Archive: server/org.jboss.tools.vscode.product/target/repository > Publish: file(s) under server/org.jboss.tools.vscode.product/distro/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23054) Build for java-language-server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23054?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23054 at 9/1/16 8:52 AM: ------------------------------------------------------------ [~nickboldt] Can you modify the job so that the content is under http://download.jboss.org/jbosstools/static/ instead. Perhaps something like http://download.jboss.org/jbosstools/static/java-language-server/$\{TIMES... [~maxandersen] Does this sound like the correct location? was (Author: gercan): [~nickboldt] Can you modify the job so that the content is under http://download.jboss.org/jbosstools/static/ instead. Perhaps something like http://download.jboss.org/jbosstools/static/java-language-server/${TIMEST... [~maxandersen] Does this sound like the correct location? > Build for java-language-server > ------------------------------ > > Key: JBIDE-23054 > URL: https://issues.jboss.org/browse/JBIDE-23054 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Gorkem Ercan > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > I need a build job that can build java-language server and publish it to download server for the use of VSCode extension. > Sources:_ https://github.com/gorkem/java-language-server_ > Build command: _mvn -Pserver-distro clean verify_ > Archive: server/org.jboss.tools.vscode.product/target/repository > Publish: file(s) under server/org.jboss.tools.vscode.product/distro/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4038) Devsuite bundle installer fails to install/configure CDK component on path with non-ascii character

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBDS-4038: ----------------------------------- Summary: Devsuite bundle installer fails to install/configure CDK component on path with non-ascii character Key: JBDS-4038 URL: https://issues.jboss.org/browse/JBDS-4038 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 1.1.0.GA Environment: Windows 7 Pro, x86_64, SP1 Reporter: Ondrej Dockal Assignee: Denis Golovin Priority: Critical Default installation on Non-ASCII path fails to install/configure CDK. Error from install log file: Thu, 01 Sep 2016 11:19:25 GMT-INFO: cdk - Execute command vagrant plugin install "c:\DevelopmentŠuite\cdk\plugins\landrush-1.1.2.gem" Thu, 01 Sep 2016 11:19:25 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:\\DevelopmentÅ uite\\cdk\\bin;c:\\DevelopmentÅ uite\\vagrant\\bin;c:\\DevelopmentÅ uite\\cygwin\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;c:\\DevelopmentSuite\\cdk\\bin;C:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;;c:\\DevelopmentŠuite\\vagrant\\bin;c:\\DevelopmentŠuite\\cygwin\\bin;C:\\DevelopmentŠuite\\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", "SESSIONNAME": "Console", "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", "windir": "C:\\Windows", "windows_tracing_flags": "3", "windows_tracing_logfile": "C:\\BVTBin\\Tests\\installpackage\\csilogfile.log", "__COMPAT_LAYER": "VistaSetup" }, "cwd": "c:\\DevelopmentŠuite\\cdk\\boxes" } Thu, 01 Sep 2016 11:19:25 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install "c:\DevelopmentŠuite\cdk\plugins\landrush-1.1.2.gem" <internal:gem_prelude>:1:in `require': cannot load such file -- rubygems.rb (LoadError) from <internal:gem_prelude>:1:in `<compiled>' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4038) Devsuite bundle installer fails to install/configure CDK component on path with non-ascii character

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-4038?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-4038: ----------------------------- > Devsuite bundle installer fails to install/configure CDK component on path with non-ascii character > --------------------------------------------------------------------------------------------------- > > Key: JBDS-4038 > URL: https://issues.jboss.org/browse/JBDS-4038 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 1.1.0.GA > Environment: Windows 7 Pro, x86_64, SP1 > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Priority: Critical > > Default installation on Non-ASCII path fails to install/configure CDK. > Error from install log file: > Thu, 01 Sep 2016 11:19:25 GMT-INFO: cdk - Execute command vagrant plugin install "c:\DevelopmentŠuite\cdk\plugins\landrush-1.1.2.gem" > Thu, 01 Sep 2016 11:19:25 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:\\DevelopmentÅ uite\\cdk\\bin;c:\\DevelopmentÅ uite\\vagrant\\bin;c:\\DevelopmentÅ uite\\cygwin\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;c:\\DevelopmentSuite\\cdk\\bin;C:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;;c:\\DevelopmentŠuite\\vagrant\\bin;c:\\DevelopmentŠuite\\cygwin\\bin;C:\\DevelopmentŠuite\\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", > "SESSIONNAME": "Console", > "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", > "windir": "C:\\Windows", > "windows_tracing_flags": "3", > "windows_tracing_logfile": "C:\\BVTBin\\Tests\\installpackage\\csilogfile.log", > "__COMPAT_LAYER": "VistaSetup" > }, > "cwd": "c:\\DevelopmentŠuite\\cdk\\boxes" > } > Thu, 01 Sep 2016 11:19:25 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install "c:\DevelopmentŠuite\cdk\plugins\landrush-1.1.2.gem" > <internal:gem_prelude>:1:in `require': cannot load such file -- rubygems.rb (LoadError) > from <internal:gem_prelude>:1:in `<compiled>' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4002) OpenJDK detection does not work for build 1.8.0_101

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4002?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4002. ----------------------------- Verified in B126. > OpenJDK detection does not work for build 1.8.0_101 > --------------------------------------------------- > > Key: JBDS-4002 > URL: https://issues.jboss.org/browse/JBDS-4002 > 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 > > > Because of changed format for version console output, installer cannot detect installed JVM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3981: ---------------------------------- Spec file and build script is here: https://github.com/jbdevstudio/jbdevstudio-product/tree/master/rpm > Build a new feature that omits features available from RPM install > ------------------------------------------------------------------ > > Key: JBDS-3981 > URL: https://issues.jboss.org/browse/JBDS-3981 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.1.0.GA > > Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png > > > What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22239: ------------------------------------------ [~jcantrill] ok, thanks for the clarification. Postponing this since we have to rework the patch. > Allow a user to choose to permanently update their desired replicas for their deployment > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22239 > URL: https://issues.jboss.org/browse/JBIDE-22239 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Viacheslav Kabanovich > Labels: openshift_v3 > Fix For: 4.5.0.AM1 > > > When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest: > * Adding a custom dialog in the "..to.." option > * Update to use a spinner > * Add a checkbox to 'make the change perminent' > * If checkbox=true, you should only need to update the dc if it has a configchange trigger. > * Optionally show checkbox if unable to determine the dc associated with the deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22239: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.1.Final) > Allow a user to choose to permanently update their desired replicas for their deployment > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22239 > URL: https://issues.jboss.org/browse/JBIDE-22239 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Viacheslav Kabanovich > Labels: openshift_v3 > Fix For: 4.5.0.AM1 > > > When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest: > * Adding a custom dialog in the "..to.." option > * Update to use a spinner > * Add a checkbox to 'make the change perminent' > * If checkbox=true, you should only need to update the dc if it has a configchange trigger. > * Optionally show checkbox if unable to determine the dc associated with the deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22912) Deploy Docker Wizard: Inappropriate project combo size

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22912?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22912: ------------------------------------------ [~mlabuda] doesnt have the time today (we have codefreeze) to verify this from source, [~bdshadow] tried but has problems connecting to OpenShift and I dont have FC23/GTK 3.20. We thus have to postpone this sinc it only "affects" (a limited part of our) users with FC23/GTK3.20 in a non-critical manner. > Deploy Docker Wizard: Inappropriate project combo size > ------------------------------------------------------ > > Key: JBIDE-22912 > URL: https://issues.jboss.org/browse/JBIDE-22912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Environment: Fedora 24, GTK 3 > Reporter: Marián Labuda > Assignee: Snjezana Peco > Priority: Minor > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM1 > > Attachments: deploy-to-docker-wizard-fc23.png, project_combo.png > > > In Deploy Docker Image wizard opened from context menu of a docker image is project combo stretched to left size and it does not look good. > !project_combo.png! -- 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