August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-819) Update fuse icons for 9.0.1.GA

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBTIS-819?page=com.atlassian.jira.plugin.... ] Lars Heinemann commented on JBTIS-819: -------------------------------------- Please use https://github.com/fusesource/fuseide/blob/master/editor/plugins/org.fuse... and cut a 32x32 of your choice. For the proxy wizard you can use: https://github.com/fusesource/fuseide/blob/master/editor/plugins/org.fuse... > Update fuse icons for 9.0.1.GA > ------------------------------ > > Key: JBTIS-819 > URL: https://issues.jboss.org/browse/JBTIS-819 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution, Fuse IDE > Affects Versions: 9.0.1.CR3 > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.1.GA > > > Update the fuse icons - they are out of date. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22603: ------------------------------------ [~adietish] as you are on Fedora can you try to reproduce following the steps from the screencast ? > Sometimes multiple OpenShift watch managers are periodically created and finished > --------------------------------------------------------------------------------- > > Key: JBIDE-22603 > URL: https://issues.jboss.org/browse/JBIDE-22603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Blocker > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > Attachments: openshift_watchers.ogv, watchers.png > > > Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template. > !watchers.png! > It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods. -- 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3627: ------------------------------------------- [~dgolovin] the usability problem you point to is not an end-user usability problem, correct ? the end user would not experience anything differently here if the download is changed from a specific file to a more generic "group", right ? This is purely because you want to be able to to do the check without knowing if the exact file has beta3, GA etc. in the file name. Thus this is more a feature request to have such url rather than a change/bug afaics. > 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

[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-22603 at 8/2/16 3:50 AM: --------------------------------------------------------------- I've created a screencast. At the beginning you can see I have up and running CDK in virt-manager. Then I created a new project and nodejs template-based application (it's same for EAP template-based). As you can see once project is expanded, watchers start periodically show and disappear. It break automatic updates as you can see later, once an application is up an running, from oc binary you can see pod and it's possible to show it in browser in tooling too. Automatic view update is broken also for scaling (well almost anything related to displayed resources). It is also blocking me from some other actions, e.g. working with server adapter. It's almost impossible to get server adapter to debugging state because of those watchers (and broken autoupdate of view...) was (Author: mlabuda): I've created a screencast. At the beginning you can see I have up and running CDK in virt-manager. Then I created a new project and nodejs template-based application (it's same for EAP template-based). As you can see once project is expanded, watchers start periodically show and disappear. It break automatic updates as you can see later, once an application is up an running, from oc binary you can see pod and it's possible to show it in browser in tooling too. Automatic view update is broken also for scaling (well almost anything related to displayed resources). > Sometimes multiple OpenShift watch managers are periodically created and finished > --------------------------------------------------------------------------------- > > Key: JBIDE-22603 > URL: https://issues.jboss.org/browse/JBIDE-22603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Blocker > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > Attachments: openshift_watchers.ogv, watchers.png > > > Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template. > !watchers.png! > It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22603: ---------------------------------- Attachment: openshift_watchers.ogv I've created a screencast. At the beginning you can see I have up and running CDK in virt-manager. Then I created a new project and nodejs template-based application (it's same for EAP template-based). As you can see once project is expanded, watchers start periodically show and disappear. It break automatic updates as you can see later, once an application is up an running, from oc binary you can see pod and it's possible to show it in browser in tooling too. Automatic view update is broken also for scaling (well almost anything related to displayed resources). > Sometimes multiple OpenShift watch managers are periodically created and finished > --------------------------------------------------------------------------------- > > Key: JBIDE-22603 > URL: https://issues.jboss.org/browse/JBIDE-22603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Blocker > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > Attachments: openshift_watchers.ogv, watchers.png > > > Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template. > !watchers.png! > It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-821) Remove obsolete methods from CamelEditor

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-821: --------------------------------------- Summary: Remove obsolete methods from CamelEditor Key: JBTIS-821 URL: https://issues.jboss.org/browse/JBTIS-821 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Reporter: Andrej Podhradsky Assignee: Tomáš Sedmík Some methods in CamelEditor don't work due to the changes in Fuse Tooling. Especially those with setting properties in Properties view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22603: ------------------------------------ [~mlabuda] Can you describe the exact steps to reproduce as we are several people not managing to reproduce it. > Sometimes multiple OpenShift watch managers are periodically created and finished > --------------------------------------------------------------------------------- > > Key: JBIDE-22603 > URL: https://issues.jboss.org/browse/JBIDE-22603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Blocker > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > Attachments: watchers.png > > > Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template. > !watchers.png! > It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22603: --------------------------------------- I've tried it yesterday with build 5681 from July 29. and I've been still able to reproduce it, unfortunately. > Sometimes multiple OpenShift watch managers are periodically created and finished > --------------------------------------------------------------------------------- > > Key: JBIDE-22603 > URL: https://issues.jboss.org/browse/JBIDE-22603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Blocker > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > Attachments: watchers.png > > > Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template. > !watchers.png! > It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22674) Refresh handler throws NPE when no active part are selected

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22674?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22674: ------------------------------------ [~adietish] can you test it ? > Refresh handler throws NPE when no active part are selected > ----------------------------------------------------------- > > Key: JBIDE-22674 > URL: https://issues.jboss.org/browse/JBIDE-22674 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.4.1.AM3 > > > EXEC: start Eclipse but don't select any part > EXEC: unfold an OS3 connection > EXEC: fill the credentials dialog > EXEC: Refresh the OS3 connection > ASSERT: the refresh handler throws NPE in the Eclipse log -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3983) DevSuite Installer proxy support

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3983: ----------------------------------- Summary: DevSuite Installer proxy support Key: JBDS-3983 URL: https://issues.jboss.org/browse/JBDS-3983 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Feature Request Components: platform-installer Affects Versions: 10.1.0.AM1 Reporter: Denis Golovin Assignee: Denis Golovin DevSuite installer cannot verify user credentials and T&C's when running in corporate network behind proxy. -- 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