November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21032) Application wizard: Parameter table is empty when new app with local templates

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21032?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21032. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > Application wizard: Parameter table is empty when new app with local templates > ------------------------------------------------------------------------------ > > Key: JBIDE-21032 > URL: https://issues.jboss.org/browse/JBIDE-21032 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: 3.1.0.Beta1-v20151023-2117-B60 > Reporter: Yue Wang > Assignee: Andre Dietisheim > Priority: Critical > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > > When new app from local templates with application wizard, no parameters is displayed in Templates Parameters table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21039) Application wizard: no/wrong Details shown for local templates

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21039?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21039. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > Application wizard: no/wrong Details shown for local templates > -------------------------------------------------------------- > > Key: JBIDE-21039 > URL: https://issues.jboss.org/browse/JBIDE-21039 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: details-for-server-template.png, no-details-for-local-template.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21079) Importing OpenShift 3 application via shell menu shows empty build configs table

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21079?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21079. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > Importing OpenShift 3 application via shell menu shows empty build configs table > -------------------------------------------------------------------------------- > > Key: JBIDE-21079 > URL: https://issues.jboss.org/browse/JBIDE-21079 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Fix For: 4.3.1.Beta1 > > Attachments: no-build-configs.png > > > Table in Import OpenShift Application wizard is empty when trying to import an OpenShift application via shell menu File - Import - Existing OpenShift Application. It is necessary to hit Refresh button to get any build config to the table and making it possible to import an application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21140) [application wizard] 2 connections from same server but for different users result in project mismatch

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21140?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21140: ---------------------------------- Fix Version/s: (was: 4.3.1.Beta1) > [application wizard] 2 connections from same server but for different users result in project mismatch > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21140 > URL: https://issues.jboss.org/browse/JBIDE-21140 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: application_wizard, upstream > Fix For: 4.4.0.Alpha1 > > > In JBT, connecting 2 users on the same server, results in wrong projects being shown for the 2nd connection (in the new application wizard). > This is caused by calling Connection.ownResource(project), having > {code} > public boolean ownsResource(IResource resource) { > if (resource == null) { > return false; > } > IClient client = resource.accept(new CapabilityVisitor<IClientCapability, IClient>() { > @Override > public IClient visit(IClientCapability capability) { > return capability.getClient(); > } > }, null); > return ObjectUtils.equals(this.client, client); > } > {code} > The problem is the clients are equals for both connections. A check for token equality should be performed to distinguish them -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21109) [application wizard] 2 connections from same server but for different users result in project mismatch

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21109?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21109. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > [application wizard] 2 connections from same server but for different users result in project mismatch > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21109 > URL: https://issues.jboss.org/browse/JBIDE-21109 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: application_wizard, upstream > Fix For: 4.3.1.Beta1 > > > In JBT, connecting 2 users on the same server, results in wrong projects being shown for the 2nd connection (in the new application wizard). > This is caused by calling Connection.ownResource(project), having > {code} > public boolean ownsResource(IResource resource) { > if (resource == null) { > return false; > } > IClient client = resource.accept(new CapabilityVisitor<IClientCapability, IClient>() { > @Override > public IClient visit(IClientCapability capability) { > return capability.getClient(); > } > }, null); > return ObjectUtils.equals(this.client, client); > } > {code} > The problem is the clients are equals for both connections. A check for token equality should be performed to distinguish them -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21140) [application wizard] 2 connections from same server but for different users result in project mismatch

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21140: ------------------------------------- Summary: [application wizard] 2 connections from same server but for different users result in project mismatch Key: JBIDE-21140 URL: https://issues.jboss.org/browse/JBIDE-21140 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 In JBT, connecting 2 users on the same server, results in wrong projects being shown for the 2nd connection (in the new application wizard). This is caused by calling Connection.ownResource(project), having {code} public boolean ownsResource(IResource resource) { if (resource == null) { return false; } IClient client = resource.accept(new CapabilityVisitor<IClientCapability, IClient>() { @Override public IClient visit(IClientCapability capability) { return capability.getClient(); } }, null); return ObjectUtils.equals(this.client, client); } {code} The problem is the clients are equals for both connections. A check for token equality should be performed to distinguish them -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21140) [application wizard] 2 connections from same server but for different users result in project mismatch

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21140?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-21140. ----------------------------------- Resolution: Done > [application wizard] 2 connections from same server but for different users result in project mismatch > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21140 > URL: https://issues.jboss.org/browse/JBIDE-21140 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: application_wizard, upstream > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > In JBT, connecting 2 users on the same server, results in wrong projects being shown for the 2nd connection (in the new application wizard). > This is caused by calling Connection.ownResource(project), having > {code} > public boolean ownsResource(IResource resource) { > if (resource == null) { > return false; > } > IClient client = resource.accept(new CapabilityVisitor<IClientCapability, IClient>() { > @Override > public IClient visit(IClientCapability capability) { > return capability.getClient(); > } > }, null); > return ObjectUtils.equals(this.client, client); > } > {code} > The problem is the clients are equals for both connections. A check for token equality should be performed to distinguish them -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21109) [application wizard] 2 connections from same server but for different users result in project mismatch

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21109?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21109: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > [application wizard] 2 connections from same server but for different users result in project mismatch > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21109 > URL: https://issues.jboss.org/browse/JBIDE-21109 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: application_wizard, upstream > Fix For: 4.3.1.Beta1 > > > In JBT, connecting 2 users on the same server, results in wrong projects being shown for the 2nd connection (in the new application wizard). > This is caused by calling Connection.ownResource(project), having > {code} > public boolean ownsResource(IResource resource) { > if (resource == null) { > return false; > } > IClient client = resource.accept(new CapabilityVisitor<IClientCapability, IClient>() { > @Override > public IClient visit(IClientCapability capability) { > return capability.getClient(); > } > }, null); > return ObjectUtils.equals(this.client, client); > } > {code} > The problem is the clients are equals for both connections. A check for token equality should be performed to distinguish them -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21110) [connection wizard] empty password should be allowed

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21110?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21110. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > [connection wizard] empty password should be allowed > ---------------------------------------------------- > > Key: JBIDE-21110 > URL: https://issues.jboss.org/browse/JBIDE-21110 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.Beta1 > > > https://github.com/redhat-developer/openshift-vagrant (requires read authorization) provides a VM with OpenShift where anonymous authentication is supported, i.e. any username will be accepted (a user will be created on-the-fly) and there's no check on passwords. > However the connection wizard doesn't allow blank/empty passwords. Also it currently trims whitespaces from passwords. So one has to type in a dummy password in order to get through authentication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21009) Can not create openshift application from local template json file

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21009?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21009. --------------------------------- Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86. > Can not create openshift application from local template json file > ------------------------------------------------------------------ > > Key: JBIDE-21009 > URL: https://issues.jboss.org/browse/JBIDE-21009 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: OpenShift 3 Tools: 3.1.0.Beta1-v20151016-1836-B52 > OS: Fedora 17 & Windows 8 > Reporter: Chunyun Chen > Assignee: Andre Dietisheim > Priority: Critical > Labels: app, openshift_v3 > Fix For: 4.3.1.Beta1 > > Attachments: local_template.png > > > Can not create openshift application from local template json file -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 November 2015