February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-20751) Wizard closing dialog shown upon canceling a creation of a project in process of creating a new OpenShift 3 application

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20751?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-20751 at 2/2/16 2:15 PM: ----------------------------------------------------------------------- [~mlabuda], I believe that it was the original idea to close New Application wizard entirely if user cancelled creation of required project. Indeed, to continue he will have to click Manage Projects and then New to get back to Create Project dialog. I will suggest fix for closing wizard. If it will be decided that wizard can remain for further user input, as [~mlabuda] suggests, the solution is the more simple. Correction. There are three different cases when New Project dialog is started from New Application wizard. 1. File-> New -> OpenShift Application started; user selects connection and after Next, Select Template page is opened and dialog New Project is opened automatically (when project list is empty). In this case, New Application wizard _should not_ be closed on project creation cancel because user has the option to push Back and select another connection. 2. Context menu on connection New -> Application is started; dialog New Project is opened automatically (when project list is empty). In this case New Application wizard _should_ be closed on project creation cancel. 3. New Project dialog is started through Manage Projects link. In this case, no matter how New Application wizard is started, it _should not_ be closed if project creation is cancelled. was (Author: scabanovich): [~mlabuda], I believe that it was the original idea to close New Application wizard entirely if user cancelled creation of required project. Indeed, to continue he will have to click Manage Projects and then New to get back to Create Project dialog. I will suggest fix for closing wizard. If it will be decided that wizard can remain for further user input, as [~mlabuda] suggests, the solution is the more simple. Correction. There are three different cases when New Project dialog is started from New Application wizard. 1. File-> New -> OpenShift Application started; user selects connection and after Next, Select Template page is opened and dialog New Project is opened automatically (when project list is empty). In this case, New Application wizard _should not_ be closed on project creation cancel because user has the option to push Back and select another connection. 2. Context menu on connection New -> Application is started; dialog New Project is opened automatically (when project list is empty). In this case New Application wizard _should_ be closed on project creation cancel. 3. New Project dialog is started through Manage Projects link. In this case, no matter how New Application wizard is started, it _should not_ be closed if project creation is canceelled. > Wizard closing dialog shown upon canceling a creation of a project in process of creating a new OpenShift 3 application > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20751 > URL: https://issues.jboss.org/browse/JBIDE-20751 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Fix For: 4.3.x > > Attachments: wizard_closing.png > > > Upon canceling a New Project dialog while creating a new OpenShift Application on a connection without any project, the info dialog about closing dialog is shown. This should not be shown. > !wizard_closing.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21629) Remove 'experimental' tag from wf10

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21629?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21629: ------------------------------------- PR removes experimental label from EAP 7, not WF 10 > Remove 'experimental' tag from wf10 > ----------------------------------- > > Key: JBIDE-21629 > URL: https://issues.jboss.org/browse/JBIDE-21629 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > eom -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21629) Remove 'experimental' tag from wf10

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21629?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21629: ------------------------------------- PR is here: https://github.com/jbosstools/jbosstools-server/pull/394 > Remove 'experimental' tag from wf10 > ----------------------------------- > > Key: JBIDE-21629 > URL: https://issues.jboss.org/browse/JBIDE-21629 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > eom -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20751) Wizard closing dialog shown upon canceling a creation of a project in process of creating a new OpenShift 3 application

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20751?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-20751: ----------------------------------------------- [~mlabuda], I believe that it was the original idea to close New Application wizard entirely if user cancelled creation of required project. Indeed, to continue he will have to click Manage Projects and then New to get back to Create Project dialog. I will suggest fix for closing wizard. If it will be decided that wizard can remain for further user input, as [~mlabuda] suggests, the solution is the more simple. > Wizard closing dialog shown upon canceling a creation of a project in process of creating a new OpenShift 3 application > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20751 > URL: https://issues.jboss.org/browse/JBIDE-20751 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Fix For: 4.3.x > > Attachments: wizard_closing.png > > > Upon canceling a New Project dialog while creating a new OpenShift Application on a connection without any project, the info dialog about closing dialog is shown. This should not be shown. > !wizard_closing.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21593) Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21593?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21593: --------------------------------------- Today I was able to spot this again. I checked .log immediately after this happened, but there was nothing. It happened on a connection to CDK. > Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21593 > URL: https://issues.jboss.org/browse/JBIDE-21593 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: Fedora 22, GTK 3. > Reporter: Marián Labuda > Labels: application_wizard, explorer, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: empty_project.png > > > When I am opening a new OpenShift application wizard on OpenShift 3 connection where are no projects yet, at first project dialog to create a new project is opened. Upon creation of a new project, dialog is closed and I am "redirected" back to application wizard, where newly created project should be preselected. Problem is the new project is shown as empty tree item in OpenShift explorer (this happens also if new project dialog is opened directly from the context menu of a clean connection) what makes new OpenShift application wizard unusable, because there are no projects in combo, no matter what. See following screenshot > !empty_project.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21629) Remove 'experimental' tag from wf10

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21629?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21629: -------------------------------- Fix Version/s: 4.3.1.CR1 > Remove 'experimental' tag from wf10 > ----------------------------------- > > Key: JBIDE-21629 > URL: https://issues.jboss.org/browse/JBIDE-21629 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.CR1 > Reporter: Rob Stryker > Fix For: 4.3.1.CR1 > > > eom -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21629) Remove 'experimental' tag from wf10

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-21629: ----------------------------------- Summary: Remove 'experimental' tag from wf10 Key: JBIDE-21629 URL: https://issues.jboss.org/browse/JBIDE-21629 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.3.1.CR1 Reporter: Rob Stryker eom -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21629) Remove 'experimental' tag from wf10

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21629?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-21629: ----------------------------------- Assignee: Rob Stryker > Remove 'experimental' tag from wf10 > ----------------------------------- > > Key: JBIDE-21629 > URL: https://issues.jboss.org/browse/JBIDE-21629 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > eom -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov reassigned JBIDE-20935: ---------------------------------------------- Assignee: Ilya Buziuk (was: Konstantin Marmalyukov) > Central doesn't scale back after being enlarged on Windows > ---------------------------------------------------------- > > Key: JBIDE-20935 > URL: https://issues.jboss.org/browse/JBIDE-20935 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: Windows 10 > 250% UI scale > Reporter: Jan Richter > Assignee: Ilya Buziuk > Labels: ui-scaling > Fix For: 4.3.x, 4.4.x > > Attachments: central.png, JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4, screenshot-1.png > > > When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars. > Like so: > !central.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20447) 2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20447?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20447: -------------------------------------- Assignee: Alexey Kazakov (was: Konstantin Marmalyukov) > 2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component > ------------------------------------------------------------------ > > Key: JBIDE-20447 > URL: https://issues.jboss.org/browse/JBIDE-20447 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Labels: testfailure > Fix For: 4.4.x > > > *2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component:* > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_mast... > # [org.jboss.tools.foundation.ui.test.BrowserUtilTest|https://jenkins.mw.lab...] (failing for 11 builds) > # [org.jboss.tools.foundation.ui.test.BrowserUtilTest|https://jenkins.mw.lab...] (failing for 11 builds) > [Search for Test Failure JIRAs in JBIDE 4.3.0.CR1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- > * {color:red}org.jboss.tools.foundation.ui.test.BrowserUtilTest : testCreateBrowserOrLink{color} (failing for 11 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_master/786/testReport/org.jboss.tools.foundation.ui.test/BrowserUtilTest/testCreateBrowserOrLink} > <case> > <age>11</age> > <className>org.jboss.tools.foundation.ui.test.BrowserUtilTest</className> > <duration>0.268</duration> > <errorStackTrace>java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowserOrLink(BrowserUtilTest.java:51) > </errorStackTrace> > <failedSince>776</failedSince> > <name>testCreateBrowserOrLink</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} > * {color:red}org.jboss.tools.foundation.ui.test.BrowserUtilTest : testCreateBrowser{color} (failing for 11 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_master/786/testReport/org.jboss.tools.foundation.ui.test/BrowserUtilTest/testCreateBrowser} > <case> > <age>11</age> > <className>org.jboss.tools.foundation.ui.test.BrowserUtilTest</className> > <duration>0.0030</duration> > <errorStackTrace>java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:712) > at org.junit.Assert.assertNotNull(Assert.java:722) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser(BrowserUtilTest.java:32) > </errorStackTrace> > <failedSince>776</failedSince> > <name>testCreateBrowser</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 February 2016