March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25873) Runtime detection: Displayed type CDK 3.2 is confusing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25873?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25873: ------------------------------------- Fix Version/s: 4.5.3.Final > Runtime detection: Displayed type CDK 3.2 is confusing > ------------------------------------------------------ > > Key: JBIDE-25873 > URL: https://issues.jboss.org/browse/JBIDE-25873 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, openshift, runtime-detection > Affects Versions: 4.5.3.AM3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: runtime_detection > Fix For: 4.5.3.Final > > Attachments: image-2018-03-28-16-26-09-154.png > > > # ASSERT: make sure that you have a ~/.minishift folder but no server adapter defined for it > # EXEC: restart your Eclipse > Result: > You get the following dialog when Eclipse is up again: > !image-2018-03-28-16-26-09-154.png! > It's puzzling for the non-intimate user since one is wondering what detected CDK is, a 3.2 or 3.3? > A simple change for the type ex. "CDK 3.2+" would make things so much more obvious. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25873) Runtime detection: Displayed type CDK 3.2 is confusing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25873?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25873: ------------------------------------- Labels: runtime_detection (was: ) > Runtime detection: Displayed type CDK 3.2 is confusing > ------------------------------------------------------ > > Key: JBIDE-25873 > URL: https://issues.jboss.org/browse/JBIDE-25873 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, openshift, runtime-detection > Affects Versions: 4.5.3.AM3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: runtime_detection > Fix For: 4.5.3.Final > > Attachments: image-2018-03-28-16-26-09-154.png > > > # ASSERT: make sure that you have a ~/.minishift folder but no server adapter defined for it > # EXEC: restart your Eclipse > Result: > You get the following dialog when Eclipse is up again: > !image-2018-03-28-16-26-09-154.png! > It's puzzling for the non-intimate user since one is wondering what detected CDK is, a 3.2 or 3.3? > A simple change for the type ex. "CDK 3.2+" would make things so much more obvious. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25873) Runtime detection: Displayed type CDK 3.2 is confusing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25873?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25873: ------------------------------------- Description: # ASSERT: make sure that you have a ~/.minishift folder but no server adapter defined for it # EXEC: restart your Eclipse Result: You get the following dialog when Eclipse is up again: !image-2018-03-28-16-26-09-154.png! It's puzzling for the non-intimate user since one is wondering what detected CDK is, a 3.2 or 3.3? A simple change for the type ex. "CDK 3.2+" would make things so much more obvious. was: # ASSERT: make sure that you have a ~/.minishift folder but no server adapter defined for it # EXEC: restart your Eclipse Result: You get the following dialog when Eclipse is up again: !image-2018-03-28-16-26-09-154.png! It's puzzling for the non-intimate user since one is wondering what detected CDK is, a 3.2 or 3.3? A simple change for the type ex. "CDK 3.2+" would make things so much more obvious. > Runtime detection: Displayed type CDK 3.2 is confusing > ------------------------------------------------------ > > Key: JBIDE-25873 > URL: https://issues.jboss.org/browse/JBIDE-25873 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, openshift, runtime-detection > Affects Versions: 4.5.3.AM3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Attachments: image-2018-03-28-16-26-09-154.png > > > # ASSERT: make sure that you have a ~/.minishift folder but no server adapter defined for it > # EXEC: restart your Eclipse > Result: > You get the following dialog when Eclipse is up again: > !image-2018-03-28-16-26-09-154.png! > It's puzzling for the non-intimate user since one is wondering what detected CDK is, a 3.2 or 3.3? > A simple change for the type ex. "CDK 3.2+" would make things so much more obvious. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4688) DevSuite Installer Guided Development Support in DevStudio

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4688?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4688: -------------------------------- Fix Version/s: 11.3.0.GA (was: 11.x) > DevSuite Installer Guided Development Support in DevStudio > ---------------------------------------------------------- > > Key: JBDS-4688 > URL: https://issues.jboss.org/browse/JBDS-4688 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: installer > Affects Versions: 11.3.0.AM3 > Reporter: Denis Golovin > Assignee: Ondrej Dockal > Fix For: 11.3.0.GA > > > Guided Development for DevStudio is based on Eclipse cheatsheets. To show guided development items selected during DevSuite installation at first DevStudio start there should be a plug-in that would check if guided development is requested during installation and open cheatsheat generated by DevSuite installer at first start. > PR is opened here https://github.com/jbdevstudio/jbdevstudio-product/pull/488. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25681) OpenShift view: Show pods/deployments for apps without service

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25681?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25681: ------------------------------------- Labels: explorer (was: ) > OpenShift view: Show pods/deployments for apps without service > -------------------------------------------------------------- > > Key: JBIDE-25681 > URL: https://issues.jboss.org/browse/JBIDE-25681 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.3.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: explorer > Fix For: 4.5.3.Final > > > In OpenShift view it should be also possible to so chow pods, deployments...not only services, because there could be running running application without services. > Steps: > 1. Create new project > 2. Create new resource in project and use this URL for pod: > https://raw.githubusercontent.com/openshift/origin/master/examples/hello-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18824) Server adapter: Remove replicated start-, stop-, restart-actions, use default actions instead

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18824?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-18824. ------------------------------------ Fix Version/s: 4.5.3.Final (was: LATER) Assignee: Andre Dietisheim Resolution: Won't Fix Resolving all OpenShift 2 issues since support for OpenShift 2 faded out. > Server adapter: Remove replicated start-, stop-, restart-actions, use default actions instead > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18824 > URL: https://issues.jboss.org/browse/JBIDE-18824 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v2 > Fix For: 4.5.3.Final > > Attachments: duplicate-application-actions.png > > > In JBIDE-11903 we added Start and Stop to the Explorer and Server adapter. In the server adapter we already have default items for start, stop and restart. We should remove our items from the OpenShift submenu and use the default actions instead: > !duplicate-application-actions.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21191) Aplication wizard: remove workaround for SWT bug where controls only get visible upon resizing dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21191?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-21191. ------------------------------------ Fix Version/s: 4.5.3.Final (was: 4.5.x) Assignee: Andre Dietisheim Resolution: Won't Fix Resolving all OpenShift 2 issues since support for OpenShift 2 faded out. > Aplication wizard: remove workaround for SWT bug where controls only get visible upon resizing dialog > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-21191 > URL: https://issues.jboss.org/browse/JBIDE-21191 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1, 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v2 > Fix For: 4.5.3.Final > > > In JBIDE-21072 we applied a workaround to fix an SWT bug where controls are not visible but appear magically if you resize the dialog: https://bugs.eclipse.org/bugs/show_bug.cgi?id=465280 > We should remove this workaround once the fix makes it to SWT in upstream -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19908) v2 Application wizard: remove GTK3 workaround once Eclipse bugzilla is resolved

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19908?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19908. ------------------------------------ Assignee: Andre Dietisheim Resolution: Won't Fix Resolving all OpenShift 2 issues since support for OpenShift 2 faded out. > v2 Application wizard: remove GTK3 workaround once Eclipse bugzilla is resolved > ------------------------------------------------------------------------------- > > Key: JBIDE-19908 > URL: https://issues.jboss.org/browse/JBIDE-19908 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1, 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: application_wizard, gtk3, openshift_v2, upstream > Fix For: 4.5.3.Final > > > In JBIDE-19853 we introduced a workaround to fix erroneous labels in GTK3. We should remove this workaround once https://bugs.eclipse.org/bugs/show_bug.cgi?id=466499 is resolved > {code:title=ApplicationTemplateWizardPage#createApplicationTemplatesViewer} > // a workaround for https://issues.jboss.org/browse/JBIDE-19853 > if (GTK3Utils.isRunning()) { > labelProvider.setOwnerDrawEnabled(false); > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25349) Renaming of existing CDK server adapter is not applied everywhere

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25349?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-25349: --------------------------------------- [~rob.stryker] I tried photon M6 eclipse bits, with installed jbosstools staging 4.5.3.AM3 update site. Do not know if this broke anything, but there are some bugs i the logic. First, I tried to apply steps to reproduce on some server adapter, ie. EAP 7.1. It works. If I tried the same procedure: # 1. Create CDK 3.2+ SA # 2. Open editor for this adapter and change the name -> SA item in Servers is renamed and editor tab as well # 3. Create new Server adapter via New Server Wizard, use default name Result: Server adapter is not created or the renamed one is renamed (not the editor tab, but only server adapter itself...) To what version of org.eclipse.wst.server plugin was this patch merged to, do you know? It is not in bugzilla. > Renaming of existing CDK server adapter is not applied everywhere > ----------------------------------------------------------------- > > Key: JBIDE-25349 > URL: https://issues.jboss.org/browse/JBIDE-25349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Fix For: 4.5.3.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25598) TP: update target platform & Central to Oxygen.3a

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25598?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25598: ------------------------------- Fix Version/s: (was: 4.5.x) > TP: update target platform & Central to Oxygen.3a > ------------------------------------------------- > > Key: JBIDE-25598 > URL: https://issues.jboss.org/browse/JBIDE-25598 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.Final > > > Switch to the latest Oxygen.3. Bits will be available starting in 4.5.3.AM2 sprint but won't be GA until 4.5.3.AM3 sprint. Then we'll move up to Oxygen.3a and Jetty 9.4.9 [1] for the Final/GA sprint. > Also need to update to Spring 3.9.3 [2] in Central. > [1] http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.4.9.v201803... > [2] http://dist.springsource.com/release/TOOLS/update/e4.7 > May need an update to 9.4.10 if it's released soon (bug fix in Fedora - ping Mat for details) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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 March 2018