February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21726) Test OpenShiftProjectCacheTest.testConnectionChanged() fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21726?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21726: ------------------------------------------ thanks! cherry-picked into jbosstools-4.3.x > Test OpenShiftProjectCacheTest.testConnectionChanged() fails > ------------------------------------------------------------ > > Key: JBIDE-21726 > URL: https://issues.jboss.org/browse/JBIDE-21726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Viacheslav Kabanovich > Labels: openshift_v3, tests > Fix For: 4.3.1.CR1 > > > 0. Connection is preset with one project. > 1. Test fires project added. OpenShiftProjectCache processes that correctly. > 2. Test requests cache.getProjectsFor(conn) - it correctly returns list with the project, but that will happen even if step 1 fails because of loading inside cache.getProjectsFor(conn) the project preset in step 0. > 3. Test fires removal of project from connection. OpenShiftProjectCache processes that correctly. > 4. Test requests cache.getProjectsFor(conn) - it incorrectly returns list with the project, though not because of step 3 failure, but by the same reason as in step 2. > Solution 1: for this test connection should return empty list of projects. > Solution 2: start with connection that has 2 projects, and before firing events call cache.getProjectsFor(conn) - that will provide the initial loading projects into cache. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21726) Test OpenShiftProjectCacheTest.testConnectionChanged() fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21726?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21726: ---------------------------------------- Assignee: Viacheslav Kabanovich Resolution: Done > Test OpenShiftProjectCacheTest.testConnectionChanged() fails > ------------------------------------------------------------ > > Key: JBIDE-21726 > URL: https://issues.jboss.org/browse/JBIDE-21726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, tests > Fix For: 4.3.1.CR1 > > > 0. Connection is preset with one project. > 1. Test fires project added. OpenShiftProjectCache processes that correctly. > 2. Test requests cache.getProjectsFor(conn) - it correctly returns list with the project, but that will happen even if step 1 fails because of loading inside cache.getProjectsFor(conn) the project preset in step 0. > 3. Test fires removal of project from connection. OpenShiftProjectCache processes that correctly. > 4. Test requests cache.getProjectsFor(conn) - it incorrectly returns list with the project, though not because of step 3 failure, but by the same reason as in step 2. > Solution 1: for this test connection should return empty list of projects. > Solution 2: start with connection that has 2 projects, and before firing events call cache.getProjectsFor(conn) - that will provide the initial loading projects into cache. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21726) Test OpenShiftProjectCacheTest.testConnectionChanged() fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21726?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21726: ------------------------------------- Labels: tests (was: ) > Test OpenShiftProjectCacheTest.testConnectionChanged() fails > ------------------------------------------------------------ > > Key: JBIDE-21726 > URL: https://issues.jboss.org/browse/JBIDE-21726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Viacheslav Kabanovich > Labels: openshift_v3, tests > Fix For: 4.3.1.CR1 > > > 0. Connection is preset with one project. > 1. Test fires project added. OpenShiftProjectCache processes that correctly. > 2. Test requests cache.getProjectsFor(conn) - it correctly returns list with the project, but that will happen even if step 1 fails because of loading inside cache.getProjectsFor(conn) the project preset in step 0. > 3. Test fires removal of project from connection. OpenShiftProjectCache processes that correctly. > 4. Test requests cache.getProjectsFor(conn) - it incorrectly returns list with the project, though not because of step 3 failure, but by the same reason as in step 2. > Solution 1: for this test connection should return empty list of projects. > Solution 2: start with connection that has 2 projects, and before firing events call cache.getProjectsFor(conn) - that will provide the initial loading projects into cache. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21726) Test OpenShiftProjectCacheTest.testConnectionChanged() fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21726?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21726: ------------------------------------- Labels: openshift_v3 tests (was: tests) > Test OpenShiftProjectCacheTest.testConnectionChanged() fails > ------------------------------------------------------------ > > Key: JBIDE-21726 > URL: https://issues.jboss.org/browse/JBIDE-21726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Viacheslav Kabanovich > Labels: openshift_v3, tests > Fix For: 4.3.1.CR1 > > > 0. Connection is preset with one project. > 1. Test fires project added. OpenShiftProjectCache processes that correctly. > 2. Test requests cache.getProjectsFor(conn) - it correctly returns list with the project, but that will happen even if step 1 fails because of loading inside cache.getProjectsFor(conn) the project preset in step 0. > 3. Test fires removal of project from connection. OpenShiftProjectCache processes that correctly. > 4. Test requests cache.getProjectsFor(conn) - it incorrectly returns list with the project, though not because of step 3 failure, but by the same reason as in step 2. > Solution 1: for this test connection should return empty list of projects. > Solution 2: start with connection that has 2 projects, and before firing events call cache.getProjectsFor(conn) - that will provide the initial loading projects into cache. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20998?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20998: ------------------------------------------ thanks! cherry-picked into jbosstools-4.3.x > Application wizard: Validation error description in Resource Labels page is cut off > ----------------------------------------------------------------------------------- > > Key: JBIDE-20998 > URL: https://issues.jboss.org/browse/JBIDE-20998 > 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.3.1.CR1 > > 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)

10 years, 1 month

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21728: ---------------------------------------- Summary: 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 Fix For: 4.3.1.CR1 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)

10 years, 1 month

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21728?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21728: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > 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)

10 years, 1 month

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20998?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-20998: ---------------------------------------- Assignee: Viacheslav Kabanovich Resolution: Done > Application wizard: Validation error description in Resource Labels page is cut off > ----------------------------------------------------------------------------------- > > Key: JBIDE-20998 > URL: https://issues.jboss.org/browse/JBIDE-20998 > 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.3.1.CR1 > > 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)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21725) Use RedDeer 1.x nightly in master builds

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21725?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21725: --------------------------------------- Thanks, [~nickboldt], we use the nightly today: https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... {code} <reddeer-stable-site>http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.0/</reddeer-stable-site> <reddeer-site>${reddeer-master-site}</reddeer-site> {code} {code} <repository> <id>reddeer-site</id> <url>${reddeer-site}</url> <layout>p2</layout> </repository> {code} So there is nothing to be done in this JIRA right now. > Use RedDeer 1.x nightly in master builds > ---------------------------------------- > > Key: JBIDE-21725 > URL: https://issues.jboss.org/browse/JBIDE-21725 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Martin said: > {quote}Nick Boldt, ok, I will discuss this with others and then get back to you - I'm not sure if now is the right time to pull a nightly or we should wait. > I think the intention was to have this in the TP so that we know exactly what is used with which version of JBT - just look in the corresponding TP. That's also how it works for server depending on base - it's the same version. But pointing to RedDeer master repo is different. > After discussion with Rastislav Wagner, here's our proposal: What if we stick with RedDeer master repo in our pom for integration tests master? For maintenance branch (4.3.x), it's good that we have a stable version of RedDeer in the TP and we can use that. But for JBT master, we can rely on the RedDeer master repo directly and later when we start testing JBT 4.4.0.Alpha1, we may put some version of RedDeer to the TP and switch to that. > What do you think? Makes sense? > So if you agree, this would mean that for now we won't use RedDeer in TP 4.60.0 - so either you can just leave it there until we replace it with a new version, or you could even remove it.{quote} > Nick said: > {quote}Makes sense. When stable, add to TP; until stable, just use nightly. > Re: updating 4.60.0.Alpha1, unless there's a compelling reason to remove it from the TP, I'm good to leave 1.0.1 in there [1]. > [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... > Let me know if you need assistance setting up your pom to depend on Red Deer 1.x nightly URL.{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3601) No splash screen during JBDS 8.x startup on Windows

by Lyle Wang (JIRA)

Lyle Wang created JBDS-3601: ------------------------------- Summary: No splash screen during JBDS 8.x startup on Windows Key: JBDS-3601 URL: https://issues.jboss.org/browse/JBDS-3601 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 8.1.0.GA Environment: WIndows 7 (RHEV VM) + Oracle JDK 7 Reporter: Lyle Wang After a typical installation, when trying to startup JBDS 8 / 8.1, there is no splash screen (and loading progress bar) before showing up the JBDS main window. -- 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 February 2016