April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3789) Installer - "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments"

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3789?page=com.atlassian.jira.plugin.... ] Pavol Pitonak commented on JBDS-3789: ------------------------------------- [~akazakov], this build? http://cdk-builds.usersys.redhat.com/builds/weekly/13-Apr-2016.rc3/cdk.zip > Installer - "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments" > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3789 > URL: https://issues.jboss.org/browse/JBDS-3789 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > Attachments: install.log, install_fail.png, log, vagrant.log, vbox.log > > > This issue is being seen with the Setup-bundled-0.0.2-20160411-98 installer > After an apparently clean/successful install, starting the CDK runtime as a server fails with this error: > Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments > Log files and screenshot are attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3729) Wrong installer icon and metadata

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3729?page=com.atlassian.jira.plugin.... ] Pavol Pitonak commented on JBDS-3729: ------------------------------------- We can probably close this issue # icon is implemented # metadata are almost done (there is a new issue JBDS-3804) # file name should be different on developers.redhat.com > Wrong installer icon and metadata > --------------------------------- > > Key: JBDS-3729 > URL: https://issues.jboss.org/browse/JBDS-3729 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Hardy Ferentschik > Attachments: installer-icon.png, installer-meta.png > > > The installer icon needs styling and the meta information needs to be set properly. See _FileDescription_ and _Company_ in attached screenshot. Also the name of the installer should be adjusted - _Setup-bundled-0.0.2-20160324-_ - it should be the proper product name + a simple version string. -- 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 Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3759?page=com.atlassian.jira.plugin.... ] Len DiMaggio edited comment on JBDS-3759 at 4/14/16 9:53 AM: ------------------------------------------------------------- +1, that's fine. was (Author: ldimaggio): +!, that's fine. > 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] (TOOLSDOC-720) JBDS 9.1 GA: Installer - Advise users to enable virt

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-720?page=com.atlassian.jira.plug... ] Len DiMaggio commented on TOOLSDOC-720: --------------------------------------- It looks great - I'd say that it can be closed. Thx! > 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] (JBDS-3759) Installer - Documentation should advise user to run commands from the correct directory

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3759?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3759: ------------------------------------ +!, that's fine. > 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] (JBIDE-22175) Warnings in JBDS after importing kitchensink-jsp quickstart

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22175?page=com.atlassian.jira.plugi... ] Sande Gilda updated JBIDE-22175: -------------------------------- Project: Tools (JBoss Tools) (was: JBoss Enterprise Application Platform) Key: JBIDE-22175 (was: JBEAP-4213) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Status: Open (was: New) Component/s: (was: Quickstarts) Target Release: (was: 7.0.0.GA) Affects Version/s: (was: 7.0.0.CR1) (was: 7.0.0.ER7) > Warnings in JBDS after importing kitchensink-jsp quickstart > ----------------------------------------------------------- > > Key: JBIDE-22175 > URL: https://issues.jboss.org/browse/JBIDE-22175 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Sande Gilda > Assignee: Alexey Kazakov > > After importing the quickstart into JBDS, the following warnings are produced > * The tag handler class for "c:forEach" (org.apache.taglibs.standard.tag.rt.core.ForEachTag) was not found on the Java Build Path > * The tag handler class for "c:out" (org.apache.taglibs.standard.tag.rt.core.OutTag) was not found on the Java Build Path -- 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 Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3801?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3801: ------------------------------------ Is it possible that a Windows dialog is being opened and is timing out - while you are away from the screen? Has the installer ever completed 100% on your Windows box? Thx! > 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: Feature Request > 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] (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: --------------------------------- [~hardy.ferentschik], [~fbricon]: can either of you lock down what we want to recommend to users as the official minimum and required specs please? I need to finalize this today. > 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] (JBIDE-22170) Openshift 3 plugin should allow me to edit Routes

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22170?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22170: --------------------------------------- Actually there is a way to edit Route. Select a project in OpenShift Explorer view, open its properties and in Properties view select Tabbed property Routes and select the desired one. Then open context menu of a route by right click and select Edit... Plain text editor (or json editor if installed) will be opened and you can change it in json directly, save changes and it immediately changes in OpenShift Explorer view as well and it is working. > Openshift 3 plugin should allow me to edit Routes > ------------------------------------------------- > > Key: JBIDE-22170 > URL: https://issues.jboss.org/browse/JBIDE-22170 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Rafael Benevides > Fix For: 4.4.x > > > - As a developer I would like to edit existing openshift routes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22174) Deploy Image to OpenShift wizard could respect selected connection and project from OpenShift Explorer

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22174: ------------------------------------- Summary: Deploy Image to OpenShift wizard could respect selected connection and project from OpenShift Explorer Key: JBIDE-22174 URL: https://issues.jboss.org/browse/JBIDE-22174 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Priority: Minor When opening Deploy Image to OpenShift wizard via context menu of a docker image in Docker Explorer, selected project (or a connection if no project under a connection is selected) should be selected in combo in the wizard. At the moment, if there is precisely 1 connection, it is selected (if there are more connections, no connection is selected and following steps is not reachable) and if there is precisely 1 project, that one is selected (if there are more projects, no project is selected). This could be refined a bit. In case of selection would be the selected one in combo. In case of existence of more connections/projects and no selection, maybe the first one listed could be selected (but this is probably personal preference, maybe it is not a good idea). -- 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