April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22260) Change 'Manage projects...' links to "New Project" buttons

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22260?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22260: --------------------------------------- So basically it should open Create New Project dialog instead of Manage Projects. Similar as we have when opening a New OpenShift Application Wizard with no projects on a connection. In that case a dialog to create a new project is opened (it could be probably reused here if possible to avoid duplicate code). > Change 'Manage projects...' links to "New Project" buttons > ---------------------------------------------------------- > > Key: JBIDE-22260 > URL: https://issues.jboss.org/browse/JBIDE-22260 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Fix For: 4.4.x > > > When creating a new application or deploying a new docker image, if the user wants to create a new project, he has to: > 1- click the manage project link > 2- click the New button in the manage projects wizards to open the New project wizard > 3- fill in the project name > 4- click ok to close the new project wizard > 5- click ok to close the manage projects wizards > => project list is reloaded > This could really be more streamlined to > 1- click the New button in the root wizard to open the New project wizard > 2- fill in the project name > 3- click ok to close the new project wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22260) Change 'Manage projects...' links to "New Project" buttons

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22260?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22260: ----------------------------------------------- Then link 'New Docker connection' also has to be replaced with a button, as the argument in favour of the link was that 'Manage projects...' is implemented as link. I would suggest in both cases concise name "New..." as evident from the label before the editor. > Change 'Manage projects...' links to "New Project" buttons > ---------------------------------------------------------- > > Key: JBIDE-22260 > URL: https://issues.jboss.org/browse/JBIDE-22260 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Fix For: 4.4.x > > > When creating a new application or deploying a new docker image, if the user wants to create a new project, he has to: > 1- click the manage project link > 2- click the New button in the manage projects wizards to open the New project wizard > 3- fill in the project name > 4- click ok to close the new project wizard > 5- click ok to close the manage projects wizards > => project list is reloaded > This could really be more streamlined to > 1- click the New button in the root wizard to open the New project wizard > 2- fill in the project name > 3- click ok to close the new project wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3860) JBDS 9.1 not connecting to internet

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3860?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3860: --------------------------------- Component/s: updatesite > JBDS 9.1 not connecting to internet > ----------------------------------- > > Key: JBDS-3860 > URL: https://issues.jboss.org/browse/JBDS-3860 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.1.0.GA > Reporter: Nichola Moore > Assignee: Alexey Kazakov > Attachments: JBDS9.1_bug.png, JBDS9.1_error_log.png, JBDS9.1_whole_screen.png, jbds_error_log.txt > > > I have downloaded and installed JBDS 9.1.0 GA on to Fedora 23. > When I try to get to JBDS-IS on Red Hat Central > Software/Update I get the error shown in the attached screenshot [1] in a pop-up window. > The rest of the screen looks like the screenshot at [2] when I click OK on the pop-up window. > [1] JBDS9.1_bug.png > [2] JBDS9.1_whole_screen.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3860) JBDS 9.1 not connecting to internet

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3860?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3860: ------------------------------------ Assignee: Nick Boldt (was: Alexey Kazakov) > JBDS 9.1 not connecting to internet > ----------------------------------- > > Key: JBDS-3860 > URL: https://issues.jboss.org/browse/JBDS-3860 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.1.0.GA > Reporter: Nichola Moore > Assignee: Nick Boldt > Attachments: JBDS9.1_bug.png, JBDS9.1_error_log.png, JBDS9.1_whole_screen.png, jbds_error_log.txt > > > I have downloaded and installed JBDS 9.1.0 GA on to Fedora 23. > When I try to get to JBDS-IS on Red Hat Central > Software/Update I get the error shown in the attached screenshot [1] in a pop-up window. > The rest of the screen looks like the screenshot at [2] when I click OK on the pop-up window. > [1] JBDS9.1_bug.png > [2] JBDS9.1_whole_screen.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22255) Number of alterated OpenShift 3 Server Adapter should start from 2 not 1

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22255?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22255: ---------------------------------- Component/s: server > Number of alterated OpenShift 3 Server Adapter should start from 2 not 1 > ------------------------------------------------------------------------ > > Key: JBIDE-22255 > URL: https://issues.jboss.org/browse/JBIDE-22255 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3, server, ux > Fix For: 4.4.x > > > When I create a New OpenShift 3 Server Adapter with same details as already an existing one server adapter, new one has altered label in Server view by number in parentheses. This starts with number 1. > Example: > I am having an OS 3 Server Adapter with label "eap-app at OpenShift 3 (10.1.2.2)" then I create a new OS 3 Server Adapter with same details and I get "eap-app at OpenShift 3 (10.1.2.2) (1)", what I think is not correct, because it is already second. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22259) Debugging of OS 3 application creates a new replication controller

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22259?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-22259 at 4/27/16 1:13 PM: ---------------------------------------------------------------- Well, it is not bad, that we modify deployment config and trigger a new deployment (replication controller). What I found useless is creating so many replication controllers, even it is not necessary. In best scenario it would be nice to have only distinct replication controllers - that mean there would be just 2 replication controllers. But at the moment there will be so many rcs as Restarting in Debug and starting in normal mode (which is broken at the moment but its gonna be done in JBIDE-22066). was (Author: mlabuda): Well, it is not bad, that we modify deployment config and trigger a new deployment (replication controller). What I found useless is creating so many replication controllers, even it is not necessary. > Debugging of OS 3 application creates a new replication controller > ------------------------------------------------------------------ > > Key: JBIDE-22259 > URL: https://issues.jboss.org/browse/JBIDE-22259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > > Restart in debug on OS 3 server adapter of eap 6.4 application and related workspace project creates a new replication controller. Every time server is stopped and started, new replication controller is created (although server has been stopped and then started) and a this new replication controller is still debugging (has set debug port). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22255) Number of alterated OpenShift 3 Server Adapter should start from 2 not 1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22255?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-22255 at 4/27/16 1:13 PM: -------------------------------------------------------------- Seems like eventually, OpenShift delegates to https://github.com/jbosstools/jbosstools-server/blob/master/as/plugins/or..., so that should be a Server issue. cc [~rob.stryker]. The problem can be reproduced with regular JBoss servers was (Author: fbricon): Seems like eventually, OpenShift delegates to https://github.com/jbosstools/jbosstools-server/blob/master/as/plugins/or..., so that should be a Server issue. cc [~rob.stryker]. > Number of alterated OpenShift 3 Server Adapter should start from 2 not 1 > ------------------------------------------------------------------------ > > Key: JBIDE-22255 > URL: https://issues.jboss.org/browse/JBIDE-22255 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3, server, ux > Fix For: 4.4.x > > > When I create a New OpenShift 3 Server Adapter with same details as already an existing one server adapter, new one has altered label in Server view by number in parentheses. This starts with number 1. > Example: > I am having an OS 3 Server Adapter with label "eap-app at OpenShift 3 (10.1.2.2)" then I create a new OS 3 Server Adapter with same details and I get "eap-app at OpenShift 3 (10.1.2.2) (1)", what I think is not correct, because it is already second. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22255) Number of alterated OpenShift 3 Server Adapter should start from 2 not 1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22255?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-22255 at 4/27/16 1:12 PM: -------------------------------------------------------------- Seems like eventually, OpenShift delegates to https://github.com/jbosstools/jbosstools-server/blob/master/as/plugins/or..., so that should be a Server issue. cc [~rob.stryker]. was (Author: fbricon): Seems like eventually, OpenShift delegates to https://github.com/jbosstools/jbosstools-server/blob/master/as/plugins/or..., that that should be a Server issue. cc [~rob.stryker]. > Number of alterated OpenShift 3 Server Adapter should start from 2 not 1 > ------------------------------------------------------------------------ > > Key: JBIDE-22255 > URL: https://issues.jboss.org/browse/JBIDE-22255 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3, server, ux > Fix For: 4.4.x > > > When I create a New OpenShift 3 Server Adapter with same details as already an existing one server adapter, new one has altered label in Server view by number in parentheses. This starts with number 1. > Example: > I am having an OS 3 Server Adapter with label "eap-app at OpenShift 3 (10.1.2.2)" then I create a new OS 3 Server Adapter with same details and I get "eap-app at OpenShift 3 (10.1.2.2) (1)", what I think is not correct, because it is already second. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22255) Number of alterated OpenShift 3 Server Adapter should start from 2 not 1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22255?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22255: -------------------------------- Labels: openshift_v3 server ux (was: openshift_v3 ux) > Number of alterated OpenShift 3 Server Adapter should start from 2 not 1 > ------------------------------------------------------------------------ > > Key: JBIDE-22255 > URL: https://issues.jboss.org/browse/JBIDE-22255 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3, server, ux > Fix For: 4.4.x > > > When I create a New OpenShift 3 Server Adapter with same details as already an existing one server adapter, new one has altered label in Server view by number in parentheses. This starts with number 1. > Example: > I am having an OS 3 Server Adapter with label "eap-app at OpenShift 3 (10.1.2.2)" then I create a new OS 3 Server Adapter with same details and I get "eap-app at OpenShift 3 (10.1.2.2) (1)", what I think is not correct, because it is already second. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22259) Debugging of OS 3 application creates a new replication controller

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22259?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22259: --------------------------------------- Well, it is not bad, that we modify deployment config and trigger a new deployment (replication controller). What I found useless is creating so many replication controllers, even it is not necessary. > Debugging of OS 3 application creates a new replication controller > ------------------------------------------------------------------ > > Key: JBIDE-22259 > URL: https://issues.jboss.org/browse/JBIDE-22259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > > Restart in debug on OS 3 server adapter of eap 6.4 application and related workspace project creates a new replication controller. Every time server is stopped and started, new replication controller is created (although server has been stopped and then started) and a this new replication controller is still debugging (has set debug port). -- 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 April 2016