May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21682) Application wizard, Connection wizard: Last used connection from explorer is not preselected

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21682?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21682. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Application wizard, Connection wizard: Last used connection from explorer is not preselected > -------------------------------------------------------------------------------------------- > > Key: JBIDE-21682 > URL: https://issues.jboss.org/browse/JBIDE-21682 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: application_wizard, connection_wizard > Fix For: 4.4.0.Alpha1 > > > In JBIDE-17568 was implemented preselection of last used connection via menu File - New - OpenShift Application. But preselection of last used connection from OpenShift explorer is not working (probably has not been implemented yet). > We should provide preselection also for last used connection via OpenShift explorer. Preselection via Menu now works like this: > User has lets say 2 connections. If he opens New Application wizard via menu File - New - OpenShift Application, then first connection is preselected. He chooses second connection in opened New Application wizard (on the first page containing credentials), clicks Next button and then user clicks Cancel. Then user open New application wizard via menu File - New - OpenShift application again and second connection is preselected. > Suggested solution for explorer: > User has 2 connections and first one is used for preselection. User selects in OpenShift explorer second connection and opens New application wizard via context menu. After closing New application wizard shell (by its completion or canceling) user should get preselected second connection after opening a New Application wizard via menu File - New - OpenShift Application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21881) Updating a token for OpenShift 3 connection via Edit Connection does not update resources

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21881?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21881. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Updating a token for OpenShift 3 connection via Edit Connection does not update resources > ----------------------------------------------------------------------------------------- > > Key: JBIDE-21881 > URL: https://issues.jboss.org/browse/JBIDE-21881 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > If token storage in secure storage expires and new one is required to be able to work with OpenShift 3 connection, then updating token via Edit Connection dialog does not automatically update connection. There is still error tree item under resources saying to obtain a new token. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21728) Application wizard: Validation error description in Resource Labels page is cut off

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21728?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21728. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Application wizard: Validation error description in Resource Labels page is cut off > ----------------------------------------------------------------------------------- > > Key: JBIDE-21728 > URL: https://issues.jboss.org/browse/JBIDE-21728 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: resource_label_complete.png, resource_label_incomplete.png > > > In Resource Label dialog there is a validation error description about correct format of a label. But the validation error description is cut off. On first sight it does not look like like cut off, but after resizing a shell more text is showed. See following image of cut off description: > !resource_label_incomplete.png! > And following image contains full description after resizing to "long enough" width: > !resource_label_complete.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21952) Enforce non empty git source parameter in templates

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21952?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21952. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Enforce non empty git source parameter in templates > --------------------------------------------------- > > Key: JBIDE-21952 > URL: https://issues.jboss.org/browse/JBIDE-21952 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > Following JBIDE-21340, we need to add validation of required git source parameter property in ParameterListPage. > To find out what parameter is the git repository url you'd do: > {code} > public String getGitRepoParameterKey() { > ITemplate template = model.getSelectedTemplate(); > if (template != null) { > for(String key : new String[]{"SOURCE_REPOSITORY_URL", "GIT_URI"}) { > if (template.getParameters().containsKey(key)) { > return key; > } > } > } > return null; > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22186) Connection (wizard): OpenShift asks for a password when CDK is restarted

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22186?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22186. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Connection (wizard): OpenShift asks for a password when CDK is restarted > ------------------------------------------------------------------------ > > Key: JBIDE-22186 > URL: https://issues.jboss.org/browse/JBIDE-22186 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.3.1.CR1 > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > 1. Install JBDS 9.1 using our windows installer > 2. Start CDK. Enter your red hat accaunt/password and check "save password" > 3. CDK is started. OS connection is available. I can open it and work with it. > 4. Stop CDK. Re-start JBDS/Eclipse. > 5. Start CDK again. > 6. Go to OS explorer is try to unfold the connection. > 7. I'm being asked for the OS password for the "openshift-dev" user. I see that "save password" is not checked. > It's very confusing because if I'm not familiar with OS I have no idea what password I'm supposed to use. And this connection worked fine before I restarted Eclipse/CDK. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20506) Reorganize context menu items of a OpenShift v3 connection

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20506?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20506. --------------------------------- Resolution: Duplicate Issue Closed as a duplicate. > Reorganize context menu items of a OpenShift v3 connection > ---------------------------------------------------------- > > Key: JBIDE-20506 > URL: https://issues.jboss.org/browse/JBIDE-20506 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.x > Reporter: Marián Labuda > Assignee: Alexey Kazakov > Priority: Minor > Labels: help_wanted > Fix For: 4.4.0.Alpha1 > > > Menu items of a v3 connection has following order: > {panel} > New > Remove > Edit > --------------- > Manage Project > Show In > ----------------- > Import Application > ----------------- > Show Properties > Refresh > {panel} > we should follow same order as for v2 connection or at least keep consistency in order - at first connection managing related items (New, Edit, Remove), then project related (Manage Project), then "application" related (Show In, Import Application), then specific connection handling (Refresh) and in the end Properties. > Then submenu items of context menu item New... should be in order Connection - (Project -) Application. Not Application - Connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21228) DeploymentConfig for Deploying a docker image should point the image container to the imagestream

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21228?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21228. --------------------------------- > DeploymentConfig for Deploying a docker image should point the image container to the imagestream > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-21228 > URL: https://issues.jboss.org/browse/JBIDE-21228 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Minor > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Deploying a docker image from a local machine will create resources. When the image is pushed to OS, the DC should assume it will be namespaced to the same project in which the resources are created. Ref: https://gist.github.com/jcantrill/cb84b919e1a7a4791440#file-gistfile1-txt... > This image was deployed to the 'helloworld' namespace and the image spec should not include the original docker namespace. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20101) v3 Application wizard: layout is broken as soon as you resize the dialog

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20101?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20101. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > v3 Application wizard: layout is broken as soon as you resize the dialog > ------------------------------------------------------------------------ > > Key: JBIDE-20101 > URL: https://issues.jboss.org/browse/JBIDE-20101 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: details-wrapped.png, layout-broken.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22128. --------------------------------- Resolution: Done > Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile > --------------------------------------------------------------------------- > > Key: JBIDE-22128 > URL: https://issues.jboss.org/browse/JBIDE-22128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Marián Labuda > Labels: respin-b > Fix For: 4.3.1.CR1 > > > I have a Java project with an "openshift" maven profile that creates a ROOT.war > When I create a "Server Adapter", the openshift plugins deploys the name of the project.war > The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22128: --------------------------------------- Well the guide seems to be a bit out dated, I had followed steps but didn't get running application. Tried with different project with openshift profile and ROOT.war has been published. Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile > --------------------------------------------------------------------------- > > Key: JBIDE-22128 > URL: https://issues.jboss.org/browse/JBIDE-22128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Marián Labuda > Labels: respin-b > Fix For: 4.3.1.CR1 > > > I have a Java project with an "openshift" maven profile that creates a ROOT.war > When I create a "Server Adapter", the openshift plugins deploys the name of the project.war > The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016