June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19960) Import wizard: Should be able to specify "Working set" when importing project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19960?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19960: ------------------------------------- Story Points: 84 (was: 8) > Import wizard: Should be able to specify "Working set" when importing project > ----------------------------------------------------------------------------- > > Key: JBIDE-19960 > URL: https://issues.jboss.org/browse/JBIDE-19960 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Priority: Minor > Labels: import_wizard, openshift_v3 > Fix For: 4.4.x > > > # ASSERT: make sure that you have package explorer set to display working sets and "Other Projects" disabled (unchecked) > # EXEC: launch import wizard > # EXEC: check if you can see you project once the import is finished. > Result: > You cannot spot your project since it was imported to "Other Projects" which is disabled. > We should allow users to specify a working set when importing a new project via Import wizard. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Remaining Estimate: 4 days (was: 2 days) > Connection wizard, Connection: should have unit tests > ------------------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.x > > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 4 days > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19738) Failed runtime download offers no error message

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19738?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19738: -------------------------------- Sprint: devex #116 June 2016 > Failed runtime download offers no error message > ----------------------------------------------- > > Key: JBIDE-19738 > URL: https://issues.jboss.org/browse/JBIDE-19738 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.3.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.x > > > While verifying JBIDE-19571 the runtime download failed and there was no error whatsoever. The download of FSW 6.0 almost started, but after a few seconds on the progress bar an error window showed up for a moment and then disappeared again and the download window was gone, too. After this, there was no error in the error view or the workspace log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Story Points: 20 (was: 16) > Connection wizard, Connection: should have unit tests > ------------------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.x > > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 2 days > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Story Points: 40 (was: 20) > Connection wizard, Connection: should have unit tests > ------------------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.x > > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 2 days > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20753) Text flickering when selecting server types in New Server wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20753?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20753: ------------------------------------- [~snjeza] ping ^^ > Text flickering when selecting server types in New Server wizard > ---------------------------------------------------------------- > > Key: JBIDE-20753 > URL: https://issues.jboss.org/browse/JBIDE-20753 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Labels: regression > Fix For: 4.4.x > > > When you open the New Server wizard and select a server type, There will be some elements rendered for a fraction of a second. It's Server Runtime Environment and a dropdown menu - it will disappear again, but it's not nice to see something quickly appear and disappear again. You can keep selecting server types and it will keep happening. All of this is on the first page of the dialog. > I checked and this did not happen in Beta2. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3905) Add JSDT/Equinox hook for Nashorn to devstudio product configuration

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-3905?page=com.atlassian.jira.plugin.... ] Pavol Srna closed JBDS-3905. ---------------------------- Haven't seen any issues so far. Closing. > Add JSDT/Equinox hook for Nashorn to devstudio product configuration > -------------------------------------------------------------------- > > Key: JBDS-3905 > URL: https://issues.jboss.org/browse/JBDS-3905 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, javascript > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 10.0.0.GA > > > We should add -Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension to the devstudio product configuration to have JSDT working OOTB. > See https://wiki.eclipse.org/JSDT/Equinox_hook_for_Nashorn -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22458) JBoss Help should use DCP v2

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22458?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-22458. ------------------------------ Verified in JBT 4.4.0.Final-a. Closing. > JBoss Help should use DCP v2 > ----------------------------- > > Key: JBIDE-22458 > URL: https://issues.jboss.org/browse/JBIDE-22458 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, common/jst/core > Affects Versions: 4.4.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Final > > > The DCPv1 search service is being phased out in favor of DCPv2. The JBoss Help feature needs to migrate to v2 as well. > - the search url needs to be changed to http://dcp2.jboss.org/v2/rest/search?size=100&query={expression}&sys_type... in org.jboss.tools.central/plugin.xml > - The JSON Parser needs to be updated to the new result format (fields are returned as arrays, we need to get the 1st element now). See https://github.com/jbosstools/jbosstools-base/blob/e0b10e225f070bc11aa1bf... > Bad news is JBDS 9/ JBT 4.3 help search will break as soon as DCPv1 is decommissioned, since the search URL is hard coded in the plugin.xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21828: ------------------------------------- Please check if JBIDE-21668 is fixed along this change > OpenShift Explorer view flickers when refreshing a service > ---------------------------------------------------------- > > Key: JBIDE-21828 > URL: https://issues.jboss.org/browse/JBIDE-21828 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Thomas Mäder > Fix For: 4.4.x > > Attachments: Screenshot 2016-03-08 10.32.39.png > > > When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls. > Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod. > Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services. > Custom/added logs in the console: > {code} > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19506: -------------------------------- Sprint: devex #116 June 2016 > Connection wizard, Connection: should have unit tests > ------------------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.x > > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 2 days > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016