March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21841) Shortened repo URL in Import wizard is weird

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21841?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21841 at 3/9/16 9:44 AM: ------------------------------------------------------------------ [~mlabuda] I agree on the sytling but not on the shortening. Without the shortening I ended up scrolling to discover the end, since that was usually what told me if I was using the right build config. The shortening is done on purpose in the middle since the parts that allow you to identify a url usually are the beginning (host, openshift-server) and the end (the specific build resource). The only enhancement I see that makes sense imho is to measure how much room there is and adapt the shortening, showing the whole string if there's enough room. And then tooltip should show the full url was (Author: adietish): [~mlabuda] I agree on the sytling but not on the shortening. Without the shortening I ended up scrolling to discover the end, since that was usually what told me if I was using the right build config. The shortening is done on purpose in the middle since the parts that allow you to identify a url usually are the beginning (host, openshift-server) and the end (the specific build resource). The only enhancement I see that makes sense imho is to measure how much room there is and adapt the shortening, showing the whole string if there's enough room > Shortened repo URL in Import wizard is weird > -------------------------------------------- > > Key: JBIDE-21841 > URL: https://issues.jboss.org/browse/JBIDE-21841 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: import_wizard, openshift_v3 > Attachments: shortened_repo_url.png > > > When Importing an OpenShift 3 application via File - Import - Existing OpenShift Application, there is a wizard page to select a build config to import application repo. We should display repo name as styled text with style (grayed) and it should not be shorten or at least not like this when there is missing a part in the middle of URL. > !shortened_repo_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21841) Shortened repo URL in Import wizard is weird

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21841?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21841: ------------------------------------------ [~mlabuda] I agree on the sytling but not on the shortening. Without the shortening I ended up scrolling to discover the end, since that was usually what told me if I was using the right build config. The shortening is done on purpose in the middle since the parts that allow you to identify a url usually are the beginning (host, openshift-server) and the end (the specific build resource). The only enhancement I see that makes sense imho is to measure how much room there is and adapt the shortening, showing the whole string if there's enough room > Shortened repo URL in Import wizard is weird > -------------------------------------------- > > Key: JBIDE-21841 > URL: https://issues.jboss.org/browse/JBIDE-21841 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: import_wizard, openshift_v3 > Attachments: shortened_repo_url.png > > > When Importing an OpenShift 3 application via File - Import - Existing OpenShift Application, there is a wizard page to select a build config to import application repo. We should display repo name as styled text with style (grayed) and it should not be shorten or at least not like this when there is missing a part in the middle of URL. > !shortened_repo_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21837) OpenShift server adpter editor: link 'Open launch configuration' throws exception

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21837?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21837: ----------------------------------------------- [~adietish], I had it on my 'fake' v3 too, fix is for both v2 and v3. > OpenShift server adpter editor: link 'Open launch configuration' throws exception > --------------------------------------------------------------------------------- > > Key: JBIDE-21837 > URL: https://issues.jboss.org/browse/JBIDE-21837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: openshift_v2, server_adapter_editor > Fix For: 4.4.0.Alpha1 > > Attachments: ErrorAtEditLaunchConfig.png > > > There is no launch configuration tab groups bound to the openshift launch type. > As the result, an exception is caught at opening 'Edit Configuration' wizard. The exception is not logged, but user has to click OK on two successive Error and Problem occurred message dialogs and finally gets the wizard with empty Name input and error message 'A name is required for the configuration'. > This user unfriendly behaviour may be considered an upstream issue, but the workaround is just to bind an empty list of tab groups. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21307) Server Adapter: ensure oc binary that's used for rsync is v1.1.1+

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21307?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21307: --------------------------------------------- I would say having actual output and error handling of the call to oc gives much more transparency. > Server Adapter: ensure oc binary that's used for rsync is v1.1.1+ > ----------------------------------------------------------------- > > Key: JBIDE-21307 > URL: https://issues.jboss.org/browse/JBIDE-21307 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: oc_binary, openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Because of https://github.com/openshift/origin/issues/6109 publishing with the server adapter (which does a oc rsync behind the scenes) only properly works with oc v1.1.1. Versions below require the user to manually > {code} > oc login --server=<server that we publish to> --token=... > {code} > We should check the version and warn if the user is using an oc that is older than this. > the changelog of oc in [v1.1.1|https://github.com/openshift/origin/releases/tag/v1.1.1] states the following refering to the issue: > {quote} > Support some of the global rsync flags on oc rsync for displaying progress information - not supported on all rsync backends (like tar) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21842) OpenShift server adpter editor: link 'Open launch configuration' throws exception

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21842?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21842: ------------------------------------------ cherry-picked into jbosstools-4.3.x > OpenShift server adpter editor: link 'Open launch configuration' throws exception > --------------------------------------------------------------------------------- > > Key: JBIDE-21842 > URL: https://issues.jboss.org/browse/JBIDE-21842 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: openshift_v2, server_adapter_editor > Fix For: 4.3.1.CR1 > > Attachments: ErrorAtEditLaunchConfig.png > > > There is no launch configuration tab groups bound to the openshift launch type. > As the result, an exception is caught at opening 'Edit Configuration' wizard. The exception is not logged, but user has to click OK on two successive Error and Problem occurred message dialogs and finally gets the wizard with empty Name input and error message 'A name is required for the configuration'. > This user unfriendly behaviour may be considered an upstream issue, but the workaround is just to bind an empty list of tab groups. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21842) OpenShift server adpter editor: link 'Open launch configuration' throws exception

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21842?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21842: ------------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.4.0.Alpha1) > OpenShift server adpter editor: link 'Open launch configuration' throws exception > --------------------------------------------------------------------------------- > > Key: JBIDE-21842 > URL: https://issues.jboss.org/browse/JBIDE-21842 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: openshift_v2, server_adapter_editor > Fix For: 4.3.1.CR1 > > Attachments: ErrorAtEditLaunchConfig.png > > > There is no launch configuration tab groups bound to the openshift launch type. > As the result, an exception is caught at opening 'Edit Configuration' wizard. The exception is not logged, but user has to click OK on two successive Error and Problem occurred message dialogs and finally gets the wizard with empty Name input and error message 'A name is required for the configuration'. > This user unfriendly behaviour may be considered an upstream issue, but the workaround is just to bind an empty list of tab groups. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21842) OpenShift server adpter editor: link 'Open launch configuration' throws exception

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21842: ---------------------------------------- Summary: OpenShift server adpter editor: link 'Open launch configuration' throws exception Key: JBIDE-21842 URL: https://issues.jboss.org/browse/JBIDE-21842 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta2 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.4.0.Alpha1 There is no launch configuration tab groups bound to the openshift launch type. As the result, an exception is caught at opening 'Edit Configuration' wizard. The exception is not logged, but user has to click OK on two successive Error and Problem occurred message dialogs and finally gets the wizard with empty Name input and error message 'A name is required for the configuration'. This user unfriendly behaviour may be considered an upstream issue, but the workaround is just to bind an empty list of tab groups. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21828: --------------------------------------- It sounds like the short term solution that may resolve much of this is to revert the changes in the ConnectionRegistry to not notify async. This was something I added as part of making the delete project issue go away, but I don't believe it is integral to a solution for that. There are probably better ways to manage the content provider and this may be one of them; I have never been fond of the design. My suggestion is to start with reverting the changes and work towards these other changes as a refactoring effort, if they make sense. > OpenShift Explorer view flickers when refreshing a service > ---------------------------------------------------------- > > Key: JBIDE-21828 > URL: https://issues.jboss.org/browse/JBIDE-21828 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Attachments: Screenshot 2016-03-08 10.32.39.png > > > When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls. > Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod. > Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services. > Custom/added logs in the console: > {code} > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21386) Create and use Neon M5 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21386?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21386: ------------------------------------ PR to update central TP - note that this removes org.eclipse.equinox.weaving.sdk.feature.group because it's not in Neon.M5: https://github.com/jbosstools/jbosstools-discovery/pull/328 Unsure if this is the best solution here; haven't tried to do a full install of Central to see if this breaks SpringIDE. Maybe it's time to grab a newer version? > Create and use Neon M5 target platform > -------------------------------------- > > Key: JBIDE-21386 > URL: https://issues.jboss.org/browse/JBIDE-21386 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: jbds-tp-p2diff-460-summary.txt, jbds-tp-p2diff-460.txt, jbt-tp-p2diff-460-summary.txt, jbt-tp-p2diff-460.txt, jbtcentral-p2diff_460.txt > > > Prepare TP to use Neon M5 bits. Cloned from JBIDE-20976 so I can start a fresh issue. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build; > * update install/matrix jobs to use new Eclipse JEE/platform binary; > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21837) OpenShift server adpter editor: link 'Open launch configuration' throws exception

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21837?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21837: ------------------------------------------ [~scabanovich] thanks! merged into master > OpenShift server adpter editor: link 'Open launch configuration' throws exception > --------------------------------------------------------------------------------- > > Key: JBIDE-21837 > URL: https://issues.jboss.org/browse/JBIDE-21837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: openshift_v2, server_adapter_editor > Fix For: 4.4.0.Alpha1 > > Attachments: ErrorAtEditLaunchConfig.png > > > There is no launch configuration tab groups bound to the openshift launch type. > As the result, an exception is caught at opening 'Edit Configuration' wizard. The exception is not logged, but user has to click OK on two successive Error and Problem occurred message dialogs and finally gets the wizard with empty Name input and error message 'A name is required for the configuration'. > This user unfriendly behaviour may be considered an upstream issue, but the workaround is just to bind an empty list of tab groups. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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