August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22822) Create New and Noteworthy for 4.4.1.AM2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22822?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22822. --------------------------------- > Create New and Noteworthy for 4.4.1.AM2 > --------------------------------------- > > Key: JBIDE-22822 > URL: https://issues.jboss.org/browse/JBIDE-22822 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.4.1.AM2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22810: --------------------------------------- I was trying to reproduce it on Fedora 24. I will give it a shot on Win 10 too. Maybe it's something platform specific... > OpenShift Explorer: empty at start > ---------------------------------- > > Key: JBIDE-22810 > URL: https://issues.jboss.org/browse/JBIDE-22810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Viacheslav Kabanovich > Fix For: 4.4.1.AM3 > > Attachments: EmptyViewAtStart.png > > > When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections. > I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22810 at 8/2/16 6:23 AM: ------------------------------------------------------------------ I had this happening in Windows quite a few times, too, when working from current master. Not all sure though how to reproduce at 100% was (Author: adietish): I had this happening in Windows quite a few times, too. Not all sure though how to reproduce at 100% > OpenShift Explorer: empty at start > ---------------------------------- > > Key: JBIDE-22810 > URL: https://issues.jboss.org/browse/JBIDE-22810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Viacheslav Kabanovich > Fix For: 4.4.1.AM3 > > Attachments: EmptyViewAtStart.png > > > When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections. > I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22451) Tests: Improve test coverage in OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22451?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22451: ------------------------------------- Sprint: devex #119 August 2016 (was: devex #118 July 2016) > Tests: Improve test coverage in OpenShift > ----------------------------------------- > > Key: JBIDE-22451 > URL: https://issues.jboss.org/browse/JBIDE-22451 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.x > > > Test coverage in OpenShift is far too poor. We have to increase it dramatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22810: ------------------------------------------ I had this happening in Windows quite a few times, too. Not all sure though how to reproduce at 100% > OpenShift Explorer: empty at start > ---------------------------------- > > Key: JBIDE-22810 > URL: https://issues.jboss.org/browse/JBIDE-22810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Viacheslav Kabanovich > Fix For: 4.4.1.AM3 > > Attachments: EmptyViewAtStart.png > > > When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections. > I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22868) Import Wizard: Last used git clone location is not used

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22868?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22868: ---------------------------------- Labels: import_wizard openshift_v3 (was: ) > Import Wizard: Last used git clone location is not used > ------------------------------------------------------- > > Key: JBIDE-22868 > URL: https://issues.jboss.org/browse/JBIDE-22868 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Labels: import_wizard, openshift_v3 > > When importing an OpenShift 3 application, I can customize where to clone source code. If I change it from default git clone location to something different. e.g. /home/mlabuda/git/alt instead of /home/mlabuda/git, the new value is used all the time. Problem is, when I decide to use default git clone location again so I check the checkbox to use that one. But this choice is not remembered and every time custom location is used. So I have to change it manually by checking the checkbox all the time. > I think, if user want to use customized location all the time he should change it in git preferences. So it would be compatible across whole IDE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22868) Import Wizard: Last used git clone location is not used

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22868: ------------------------------------- Summary: Import Wizard: Last used git clone location is not used Key: JBIDE-22868 URL: https://issues.jboss.org/browse/JBIDE-22868 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.1.AM3 Reporter: Marián Labuda When importing an OpenShift 3 application, I can customize where to clone source code. If I change it from default git clone location to something different. e.g. /home/mlabuda/git/alt instead of /home/mlabuda/git, the new value is used all the time. Problem is, when I decide to use default git clone location again so I check the checkbox to use that one. But this choice is not remembered and every time custom location is used. So I have to change it manually by checking the checkbox all the time. I think, if user want to use customized location all the time he should change it in git preferences. So it would be compatible across whole IDE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3977) Devstudio version string needs update

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3977?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3977: ------------------------------ Story Points: 1 Sprint: devex #118 July 2016 > Devstudio version string needs update > ------------------------------------- > > Key: JBDS-3977 > URL: https://issues.jboss.org/browse/JBDS-3977 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Jan Richter > Assignee: Jan Richter > > As per requirements.json, the static version field for devstudio is still set to 10.0.1.Alpha1. We need to update this and preferably find some way to do this effortlessly any time the version changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3977) Devstudio version string needs update

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3977?page=com.atlassian.jira.plugin.... ] Jan Richter reassigned JBDS-3977: --------------------------------- Assignee: Jan Richter > Devstudio version string needs update > ------------------------------------- > > Key: JBDS-3977 > URL: https://issues.jboss.org/browse/JBDS-3977 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Jan Richter > Assignee: Jan Richter > > As per requirements.json, the static version field for devstudio is still set to 10.0.1.Alpha1. We need to update this and preferably find some way to do this effortlessly any time the version changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

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

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] David Hladky commented on JBDS-3627: ------------------------------------ BTW: Did you know that if you use https://developers.redhat.com/download-manager/rest/available/ , you can get information about the terms and conditions model being used, the files under the specific product etc. If you want to use it, I suggest to narrow the query to filter out not necessary information. By adding product code after the link, you can narrow the response to just the product you are interested in. By adding a query paramter nv=<number> you can decrease the number of versions returned (only number of latest versions will be returned). > 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.1.0.AM3 > > Attachments: Installer-not-signed-tc.PNG > > > DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689. > DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification: > 1. that provided credentials are valid; > 2. that required T&C's are signed. > There are two major use cases for developers installing DevSuite using Installer: > 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf; > 2. Shared installer - when someone share installer with developers without account. > There two kind of users involved in those scenarios above: > 1. New users that must go through registration process; > 2. Registered users. > *Direct download* > For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation. > For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579. > So far there are two kind of problems: > 1. Users can login and download DevSuite installer, but cannot use the same credentials to install; > 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used > *Shared Download* > In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation. > Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 August 2016