April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3801) installer never completes if left running while screen times out

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3801?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3801: -------------------------------------- [~mhusnain] are you using the small installer which downloads everything? The small installer is not functional at this point. We won't release it. We will release the big installer (1.6GB) which bundles everything but Vagrant and VirtualBox. > installer never completes if left running while screen times out > ---------------------------------------------------------------- > > Key: JBDS-3801 > URL: https://issues.jboss.org/browse/JBDS-3801 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Environment: Windows 10 PRo on a Surface. > Reporter: Misha Ali > Assignee: Denis Golovin > Priority: Minor > Labels: Havoc > Attachments: install.log, install_new.log > > > I've tested a few times by installing and uninstalling using the new all in one installer. > If the install process is left on and the screen times out, the installer never finishes installing and stalls at 98-99% for the last three items (namely CDK, JDK and JBDS). > Not sure if this is a problem specific to this device because I've only tested on this bug logging issue just in case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3653) User's home folder with spaces cannot be used by vagrant during install

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3653?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3653: -------------------------------- Workaround Description: {color:red}use VAGRANT_HOME environment variable and set path to c:\DeveloperPlatform\vagrant\.vagrant.d or any location without spaces in name.{color} (was: use VAGRANT_DOTFILE_PATH environment variable and set path to .vargant.d folder to be located in c:\DeveloperPlatform\vagrant\.vagrant.d or any location without space in name.) > User's home folder with spaces cannot be used by vagrant during install > ----------------------------------------------------------------------- > > Key: JBDS-3653 > URL: https://issues.jboss.org/browse/JBDS-3653 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > Attachments: install(1).log > > > Vagrant complains about > {quote}Wed, 02 Mar 2016 18:04:21 GMT-ERROR: cdk - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.0.0.gem" > The 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 > {quote} > When user home directory have spaces in it, because .vagrant.d file path in turn has spaces as well. For instance: > {code}C:\Users\User Name\.vagrant.d{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3748) Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer)

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3748?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3748: --------------------------------- Thanks, Alexey. Going with the above unless anyone objects before release. > Installer - We need to define/document the minimum hardware requirements for the installer (and packages installed by the installer) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3748 > URL: https://issues.jboss.org/browse/JBDS-3748 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation, installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: havoc > Fix For: 9.1.0.GA > > > The latest information that I can find for JBDS is: > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > This is not adequate for the CDK, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3759) Installer - Documentation should advise user to run commands from the correct directory

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3759?page=com.atlassian.jira.plugin.... ] Misha Ali closed JBDS-3759. --------------------------- Resolution: Rejected Rejected since this is for CDK docs. > Installer - Documentation should advise user to run commands from the correct directory > --------------------------------------------------------------------------------------- > > Key: JBDS-3759 > URL: https://issues.jboss.org/browse/JBDS-3759 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation, installer > Affects Versions: 9.1.0.GA > Environment: Installer: Setup-bundled-0.0.2-20160401-33.exe > Reporter: Len DiMaggio > Labels: havoc > > C:\Users\jbossqa>vagrant ssh > A Vagrant environment or target machine is required to run this > command. Run `vagrant init` to create a new Vagrant environment. Or, > get an ID of a target machine from `vagrant global-status` to run > this command on. A final option is to change to a directory with a > Vagrantfile and to try again. > C:\>cd DeveloperPlatform\cdk\components\rhel\rhel-ose > C:\DeveloperPlatform\cdk\components\rhel\rhel-ose>vagrant ssh > VM must be running to open SSH connection. Run `vagrant up` > to start the virtual machine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3801) installer never completes if left running while screen times out

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3801?page=com.atlassian.jira.plugin.... ] Misha Ali updated JBDS-3801: ---------------------------- Attachment: install.log install_new.log install_new.log is the original attempt that terminated yesterday. install.log is my fresh attempt today in the default folder with older components installed and detected but JBDS, openJDK and CDK being redownloaded and installed. This also stalled at around the same point (98-99% for all three and no progress after). > installer never completes if left running while screen times out > ---------------------------------------------------------------- > > Key: JBDS-3801 > URL: https://issues.jboss.org/browse/JBDS-3801 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Environment: Windows 10 PRo on a Surface. > Reporter: Misha Ali > Assignee: Denis Golovin > Priority: Minor > Labels: Havoc > Attachments: install.log, install_new.log > > > I've tested a few times by installing and uninstalling using the new all in one installer. > If the install process is left on and the screen times out, the installer never finishes installing and stalls at 98-99% for the last three items (namely CDK, JDK and JBDS). > Not sure if this is a problem specific to this device because I've only tested on this bug logging issue just in case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3801) installer never completes if left running while screen times out

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3801?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3801: --------------------------------- The installer did complete initially. I've done the install/uninstall a few times to test iterative versions of the installer, so maybe there is something left over in cleanup during uninstall, or there is just something odd about timeout. Attaching log in a second, I just started it again earlier to test and it looks like it's stuck at the same point for some time now. > installer never completes if left running while screen times out > ---------------------------------------------------------------- > > Key: JBDS-3801 > URL: https://issues.jboss.org/browse/JBDS-3801 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Environment: Windows 10 PRo on a Surface. > Reporter: Misha Ali > Assignee: Denis Golovin > Priority: Minor > Labels: Havoc > > I've tested a few times by installing and uninstalling using the new all in one installer. > If the install process is left on and the screen times out, the installer never finishes installing and stalls at 98-99% for the last three items (namely CDK, JDK and JBDS). > Not sure if this is a problem specific to this device because I've only tested on this bug logging issue just in case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-720) JBDS 9.1 GA: Installer - Advise users to enable virt

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-720?page=com.atlassian.jira.plug... ] Misha Ali resolved TOOLSDOC-720. -------------------------------- Resolution: Done Reviewed (thanks, Len!) and ready to close. > JBDS 9.1 GA: Installer - Advise users to enable virt > ---------------------------------------------------- > > Key: TOOLSDOC-720 > URL: https://issues.jboss.org/browse/TOOLSDOC-720 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: Installation Guide > Affects Versions: 9.1 GA > Reporter: Misha Ali > Assignee: Misha Ali > Labels: AIO_Installer > > From JBDS-3733: > This might be overkill, but, just in case users are running the installer on a new Windows system, they should be advised that virtualization must be enabled in the BIOS or they will not be able to start vagrant boxes. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-724) JBDS 9.1: Install Guide Update

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-724?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-724: ------------------------------------ [~supriya.bharadwaj], it would probably be easier to review if you can list the changes you have made, or point to a section that has changed a bit rather than ask for review of everything. Perhaps Len can help if Martin and Jan are busy. > JBDS 9.1: Install Guide Update > ------------------------------ > > Key: TOOLSDOC-724 > URL: https://issues.jboss.org/browse/TOOLSDOC-724 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Affects Versions: 9.1 GA > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > Labels: EAP, JBDS > Fix For: 9.1 GA > > Attachments: eap_server_select.png > > > Requirements: > 1. Review the JBDS 9.1 Beta2 install guide and test it against the JBDS 9.1 GA build to see if the installation instructions work. Update as required. > 2. [~ahoffer] has requested information about the difference between the currently documented instructions for JBDS with EAP[1] and the JBDS 9.1 GA build. Compare tested instructions in JBDS docs with those at [1] and let her know of any glaring issues, if any. > 3. Quickly create a new EAP server and confirm whether there is still a listing for "JBoss Enterprise Application Platform 7.0 (Experimental)" and let Andrea know. See screenshot here for what dialogue menu we want to check: https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise... > [1] - https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22177) Docker Image host is missing from Deployment Config when deploying from a private registry

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22177?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-22177: --------------------------------------- [~fbricon] Can you post a copy of the DC and IS that was created as part of the 'deploy image' workflow. > Docker Image host is missing from Deployment Config when deploying from a private registry > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22177 > URL: https://issues.jboss.org/browse/JBIDE-22177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha1 > > > If you deploy a docker image from myregistry:5000/example/myimage, the deployment config is generated with only example/myimage, so can't find the image to deploy -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21627) Enable exposure of OpenShift resources in tooling

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21627?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21627: --------------------------------------- [~mlabuda] ".....That is because user could create pod from json" I'm not certain in future if you will be able to directly create a pod. I recall a comment from someone saying that this was or will be policy restricted and you will only be able to create pods by defining a replication controller. > Enable exposure of OpenShift resources in tooling > ------------------------------------------------- > > Key: JBIDE-21627 > URL: https://issues.jboss.org/browse/JBIDE-21627 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.4.x > > > It would be nice if we would have something similar as oc binary to expose an existing resource. To expose existing pods or services. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016