June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3627: -------------------------------- Sprint: (was: devex #115 May 2016) > Installer needs to help move past lack of t/c signing > ----------------------------------------------------- > > Key: JBDS-3627 > URL: https://issues.jboss.org/browse/JBDS-3627 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.GA > > Attachments: Installer-not-signed-tc.PNG > > > When you login with an active account that hasn't signed the Terms and Conditions the login fails and tells you why but not how to resolve it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3618) Progress does not reflect actual amount of work done

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3618?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3618: -------------------------------- Sprint: (was: devex #115 May 2016) > Progress does not reflect actual amount of work done > ---------------------------------------------------- > > Key: JBDS-3618 > URL: https://issues.jboss.org/browse/JBDS-3618 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Labels: havoc, ui > Fix For: 10.0.0.GA > > > It seems the current way the progress tracking is implemented is simply by giving an initial time estimate for each component. The progress bars then just count down the supplied time with no relation to the actual progress achieved. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3867) CDK file name should include version, match file name on RHCP

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3867?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3867: -------------------------------- Sprint: (was: devex #115 May 2016) > CDK file name should include version, match file name on RHCP > ------------------------------------------------------------- > > Key: JBDS-3867 > URL: https://issues.jboss.org/browse/JBDS-3867 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Windows 7/64 bit > Reporter: Robert Terzi > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.0.0.GA > > > The platform installer uses a file name for the CDK box with no version information making it difficult to tell if you have the latest CDK box or not. > The downloaded box file is saved in \cdk\boxes\rhel-vagrant-virtualbox.box. > It should use the same file name as the Red Hat Customer Portal to make it easy to identify that it is the same file: rhel-cdk-kubernetes-7.2-23.x86_64.vagrant-virtualbox.box -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3938) Dvelopment Suite Installer should install sshfs vagrant plugin

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3938?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3938: -------------------------------- Story Points: 2 > Dvelopment Suite Installer should install sshfs vagrant plugin > -------------------------------------------------------------- > > Key: JBDS-3938 > URL: https://issues.jboss.org/browse/JBDS-3938 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3787. --------------------------------- Resolution: Done Fixed with https://github.com/redhat-developer-tooling/developer-platform-install/co... > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc, new_and_notworthy, user-docs > Attachments: components are optional v1.png, components are optional v2.png, screenshot-1.png > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22575) Extract CDK's Docker registry from vagrant service-manager env

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22575?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22575: -------------------------------- Description: The docker registry url is currently hard coded when created a new OpenShift connection for the CDK (JBIDE-22441). With https://github.com/projectatomic/vagrant-service-manager/issues/210 being fixed and the CDK 2.1 looming around the corner, it's now possible to get the DOCKER_REGISTRY value from the CDK: {code} vagrant service-manager env # docker env: # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export DOCKER_CERT_PATH=/Users/fbricon/Dev/openshift/cdk.old/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 # openshift env: # You can access the OpenShift console on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io {code} We should store the docker registry with a https:// prefix, if the value is not a URL was: The docker registry url is currently hard coded when created a new OpenShift connection for the CDK (JBIDE-22441). With https://github.com/projectatomic/vagrant-service-manager/issues/210 being fixed and the CDK 2.1 looming around the corner, it's now possible to get the DOCKER_REGISTRY value from the CDK: {quote} vagrant service-manager env # docker env: # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export DOCKER_CERT_PATH=/Users/fbricon/Dev/openshift/cdk.old/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 # openshift env: # You can access the OpenShift console on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io {quote} We should store the docker registry with a https:// prefix, if the value is not a URL > Extract CDK's Docker registry from vagrant service-manager env > -------------------------------------------------------------- > > Key: JBIDE-22575 > URL: https://issues.jboss.org/browse/JBIDE-22575 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.4.0.Final > > > The docker registry url is currently hard coded when created a new OpenShift connection for the CDK (JBIDE-22441). > With https://github.com/projectatomic/vagrant-service-manager/issues/210 being fixed and the CDK 2.1 looming around the corner, it's now possible to get the DOCKER_REGISTRY value from the CDK: > {code} > vagrant service-manager env > # docker env: > # Set the following environment variables to enable access to the > # docker daemon running inside of the vagrant virtual machine: > export DOCKER_HOST=tcp://10.1.2.2:2376 > export DOCKER_CERT_PATH=/Users/fbricon/Dev/openshift/cdk.old/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > export DOCKER_TLS_VERIFY=1 > export DOCKER_API_VERSION=1.21 > # openshift env: > # You can access the OpenShift console on: https://10.1.2.2:8443/console > # To use OpenShift CLI, run: oc login https://10.1.2.2:8443 > export OPENSHIFT_URL=https://10.1.2.2:8443 > export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console > export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io > {code} > We should store the docker registry with a https:// prefix, if the value is not a URL -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3936) devstudio.exe has eclipse icon

by James Cobb (JIRA)

[ https://issues.jboss.org/browse/JBDS-3936?page=com.atlassian.jira.plugin.... ] James Cobb edited comment on JBDS-3936 at 6/8/16 3:12 PM: ---------------------------------------------------------- This is the RHD website so it's exactly where it's supposed to be used. http://developers.redhat.com/products/ This usage absolutely is incorrect and needs to be pulled down immediately. https://devstudio.jboss.com/10.0/staging/updates/ This page needs to use the formal RHJBDS logotype as designed. http://brand.redhat.com/logos/productlogos/ Specifically: https://pnt.redhat.com/pnt/b-813720/Red_Hat_JBoss_Developer_Studio [~maxandersen] ^^^ the JBDS icon on the JIRA falls under the same issue as DevStudio. was (Author: james.cobb): This is the RHD website so it's exactly where it's supposed to be used. http://developers.redhat.com/products/ This usage absolutely is incorrect and needs to be pulled down immediately. https://devstudio.jboss.com/10.0/staging/updates/ This page needs to use the formal RHJBDS logotype as designed. http://brand.redhat.com/logos/productlogos/ Specifically: https://pnt.redhat.com/pnt/b-813720/Red_Hat_JBoss_Developer_Studio the JBDS icon on the JIRA falls under the same issue as DevStudio. > devstudio.exe has eclipse icon > ------------------------------ > > Key: JBDS-3936 > URL: https://issues.jboss.org/browse/JBDS-3936 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.0.0.GA > Reporter: Radim Hopp > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 10.0.0.GA > > Attachments: devstudio.ico.10.png, jbds.ico.9.1.png, jbds.ico.9.1export-layers.png, jbds.ico_vs_devstudio.ico.png > > > [installFolder]/studio/devstudio.exe has eclipse icon instead of redhat developer icon. > http://i.imgur.com/ZKjeJGC.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3936) devstudio.exe has eclipse icon

by James Cobb (JIRA)

[ https://issues.jboss.org/browse/JBDS-3936?page=com.atlassian.jira.plugin.... ] James Cobb commented on JBDS-3936: ---------------------------------- This is the RHD website so it's exactly where it's supposed to be used. http://developers.redhat.com/products/ This usage absolutely is incorrect and needs to be pulled down immediately. https://devstudio.jboss.com/10.0/staging/updates/ This page needs to use the formal RHJBDS logotype as designed. http://brand.redhat.com/logos/productlogos/ Specifically: https://pnt.redhat.com/pnt/b-813720/Red_Hat_JBoss_Developer_Studio the JBDS icon on the JIRA falls under the same issue as DevStudio. > devstudio.exe has eclipse icon > ------------------------------ > > Key: JBDS-3936 > URL: https://issues.jboss.org/browse/JBDS-3936 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.0.0.GA > Reporter: Radim Hopp > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 10.0.0.GA > > Attachments: devstudio.ico.10.png, jbds.ico.9.1.png, jbds.ico.9.1export-layers.png, jbds.ico_vs_devstudio.ico.png > > > [installFolder]/studio/devstudio.exe has eclipse icon instead of redhat developer icon. > http://i.imgur.com/ZKjeJGC.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3939) Update devsuite version number to 1.0.0-GA

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3939?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3939: ----------------------------- > Update devsuite version number to 1.0.0-GA > ------------------------------------------ > > Key: JBDS-3939 > URL: https://issues.jboss.org/browse/JBDS-3939 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3939) Update devsuite version number to 1.0.0-GA

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3939: ----------------------------------- Summary: Update devsuite version number to 1.0.0-GA Key: JBDS-3939 URL: https://issues.jboss.org/browse/JBDS-3939 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016