April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24250) OpenShift Explorer sometimes don't show the objects in Properties view

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24250?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-24250. ------------------------------ I'm not able to replicate in Devstudio 10.4.0.AM3-v20170421-0111-B478. If you stumble upon this once again, feel free to reopen. > OpenShift Explorer sometimes don't show the objects in Properties view > ---------------------------------------------------------------------- > > Key: JBIDE-24250 > URL: https://issues.jboss.org/browse/JBIDE-24250 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Final > Environment: * JBoss Developer Studio 10.2.0.GA > * CDK > Reporter: Ricardo Martinelli Oliveira > Assignee: Jeff MAURY > Fix For: 4.4.4.AM3, 4.5.0.AM1 > > Attachments: empty-builds.png > > > After right-click in a project in OpenShift Explorer view and select Properties, not always the list of Kubernetes/OpenShift objects are listed in the Properties view. The workaround I found is close all editors, the Properties view and after changing the focus on other views, go back to OpenShift Explorer and Refresh it I can finally list the objects. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4363) Installed Components detection never ends on macOS

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4363?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4363. ----------------------------- Verified in build 206. > Installed Components detection never ends on macOS > -------------------------------------------------- > > Key: JBDS-4363 > URL: https://issues.jboss.org/browse/JBDS-4363 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.AM3 > Environment: macOS > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.4.0.AM3 > > > Detection stacks because of version parsing error in OpenJDK detection -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24025) AssertionFailedException in ExpressServerUtils.getDefaultDeployFolder

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24025?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-24025. ------------------------------ As I don't have the steps to reproduce I've added auto action to AERI for reopening this jira if this problem occurs with org.jboss.tools.openshift.express.core version > 3.3.2. Closing > AssertionFailedException in ExpressServerUtils.getDefaultDeployFolder > --------------------------------------------------------------------- > > Key: JBIDE-24025 > URL: https://issues.jboss.org/browse/JBIDE-24025 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Automated Error Reporting Bot > Assignee: Andre Dietisheim > Labels: openshift_v2 > Fix For: 4.4.4.AM3, 4.5.0.AM1 > > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > org.eclipse.core.runtime.AssertionFailedException: null argument: > at org.jboss.tools.openshift.express.internal.core.server.ExpressServerUtils.getDefaultDeployFolder(ExpressServerUtils.java:292) > at org.jboss.tools.openshift.express.internal.core.server.ExpressServerUtils.getDeployFolder(ExpressServerUtils.java:264) > at org.jboss.tools.openshift.express.internal.core.server.ExpressServerUtils.getDeployFolder(ExpressServerUtils.java:260) > at org.jboss.tools.openshift.express.internal.ui.server.ExpressServerEditorSection.initWidgets(ExpressServerEditorSection.java:122) > at org.jboss.tools.openshift.express.internal.ui.server.ExpressServerEditorSection$1.run(ExpressServerEditorSection.java:103) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024) > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.eclipse.swt | 3.104.1.v20150825-0743 | 3.105.1.v20160907-0248 | > | org.eclipse.wst.server.core | 1.8.0.v201601132216 | 1.9.0.v201610211907 | > | org.jboss.tools.openshift.express.core | 3.1.0.Final-v20160414-0041-B272 | 3.3.2.v20170119-1710 | > | org.jboss.tools.openshift.express.ui | 3.1.0.Final-v20160414-0041-B272 | 3.3.1.v20161003-1104 | > Operating Systems: > | Linux | 3.13.0 | 3.13.0 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/56df0c0fe4b0e0c18a6... for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22191) Application wizard: Support list of application creation with JSON

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22191?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-22191. ------------------------------ Resolved as part of https://issues.jboss.org/browse/JBIDE-23769. Verified in Devstudio 10.4.0.AM3-v20170421-0111-B478 > Application wizard: Support list of application creation with JSON > ------------------------------------------------------------------ > > Key: JBIDE-22191 > URL: https://issues.jboss.org/browse/JBIDE-22191 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Fix For: 4.4.4.AM3 > > Attachments: screenshot-1.png > > > Currently, if we provide a Local template, which is a list of templates, there is a popup with an error. > {noformat} > java.lang.ClassCastException: com.openshift.internal.restclient.model.List cannot be cast to com.openshift.restclient.model.template.ITemplate > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.getLocalTemplate(NewApplicationWizardModel.java:107) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.updateSelectedTemplate(NewApplicationWizardModel.java:86) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.update(NewApplicationWizardModel.java:78) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.setLocalTemplateFileName(NewApplicationWizardModel.java:315) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateListPage.setLocalTemplate(TemplateListPage.java:511) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateListPage.access$6(TemplateListPage.java:506) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateListPage$14.widgetSelected(TemplateListPage.java:696) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:279) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270) > at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > {noformat} > You can use the template used by Fuse to reproduce: https://raw.githubusercontent.com/jboss-fuse/application-templates/master... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4356) cygwin cannot be installed if virtualbox has validation problems reported and unselected

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4356?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4356. ----------------------------- Verified in build 206. > cygwin cannot be installed if virtualbox has validation problems reported and unselected > ----------------------------------------------------------------------------------------- > > Key: JBDS-4356 > URL: https://issues.jboss.org/browse/JBDS-4356 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.4.0.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24123) CDK3 Server adapter: undo wont reset Hypervisor

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24123?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24123. --------------------------------- Verified in devstudio 10.4.0.AM3. > CDK3 Server adapter: undo wont reset Hypervisor > ----------------------------------------------- > > Key: JBIDE-24123 > URL: https://issues.jboss.org/browse/JBIDE-24123 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.4.AM3, 4.5.0.AM1 > > Attachments: JBIDE 24123.mp4 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24230) CDK3 server adapter: duplicate server adapter path is created upon startup

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24230?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24230: --------------------------------------- [~rob.stryker], please clarify? {quote} If a new one is discovered but has a DIFFERENT minishift path declared, then we'll mark it as new. {quote} Different than what? For me, the cdk 3 server adapter that is created automatically via runtime detection does not have any minishift binary path set up. Which seems logical to me, because there is no way the runtime detection can learn the path. So I verified the first use case - when you have this automatic server adapter and change it a bit and then restart your workspace, no new server will be created. But I'm not sure what is the circumstance where a new server would actually be created if you already have a cdk3 server present. Also, as to Andre's second use case: {quote} ASSERT: have a cdk3 server adapter EXEC: delete it EXEC: restart Eclipse {quote} There is no way to avoid this, right? As long as runtime detection finds something in ~/.minishift, it will always create a server adapter when none is present. Right? > CDK3 server adapter: duplicate server adapter path is created upon startup > -------------------------------------------------------------------------- > > Key: JBIDE-24230 > URL: https://issues.jboss.org/browse/JBIDE-24230 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.4.AM3 > > Attachments: cdk3 server adapter gets duplicated.mp4, cdk3 server adapter reappears.mp4 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23769) New Application: Do not throw exception in error log when provided template is of wrong kind.

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23769?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-23769. ------------------------------ Verified in Devstudio 10.4.0.AM3-v20170421-0111-B478. Closing. > New Application: Do not throw exception in error log when provided template is of wrong kind. > --------------------------------------------------------------------------------------------- > > Key: JBIDE-23769 > URL: https://issues.jboss.org/browse/JBIDE-23769 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > Assignee: Jeff MAURY > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.4.AM3 > > > When creating new application from local template one selects wrong file (not of kind "Template", but kind "Pod" for example) multiple (same) exceptions are thrown into error log: > {noformat} > !ENTRY org.eclipse.core.databinding 4 0 2017-01-19 13:56:20.472 > !MESSAGE Unhandled exception: Wrong resource kind: Pod > !STACK 0 > org.jboss.tools.openshift.internal.ui.wizard.newapp.NotATemplateException: Wrong resource kind: Pod > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.getLocalAppSource(NewApplicationWizardModel.java:139) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.loadAppSource(NewApplicationWizardModel.java:293) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceListPage$17.run(ApplicationSourceListPage.java:824) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > I think it's enough to inform the user in the wizard (this is already happening). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24276) CDK3 server adapter/editor: UI inconsistencies - widget order, labels

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24276?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24276. --------------------------------- Verified in devstudio 10.4.0.AM3. Both is now correct. Commit present also in master. Closing. > CDK3 server adapter/editor: UI inconsistencies - widget order, labels > --------------------------------------------------------------------- > > Key: JBIDE-24276 > URL: https://issues.jboss.org/browse/JBIDE-24276 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.4.AM3, 4.5.0.AM1 > > Attachments: editor-1location-2hypervisor.png, editor-minishift-location.png, wizard-1hypervisor-2location.png, wizard-minishift-binary.png > > > CDK3 Server adapter wizard and editor differ in labelling and widget ordering. It would be nice if those 2 could be consistent. > * the widget to set the minishift binary is labeled "Minishift Binary" in the wizard, "Minishift Location" in the editor > !wizard-minishift-binary.png! > !editor-minishift-location.png! > * the widget order in the wizard is 1) Hypervisor 2) Minishift Location while in the editor it's the opposite: 1) Minishift Location 2) Hypervisor > !editor-1location-2hypervisor.png! > !wizard-1hypervisor-2location.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24276) CDK3 server adapter/editor: UI inconsistencies - widget order, labels

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24276?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-24276: ---------------------------------- Fix Version/s: 4.5.0.AM1 > CDK3 server adapter/editor: UI inconsistencies - widget order, labels > --------------------------------------------------------------------- > > Key: JBIDE-24276 > URL: https://issues.jboss.org/browse/JBIDE-24276 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.4.AM3, 4.5.0.AM1 > > Attachments: editor-1location-2hypervisor.png, editor-minishift-location.png, wizard-1hypervisor-2location.png, wizard-minishift-binary.png > > > CDK3 Server adapter wizard and editor differ in labelling and widget ordering. It would be nice if those 2 could be consistent. > * the widget to set the minishift binary is labeled "Minishift Binary" in the wizard, "Minishift Location" in the editor > !wizard-minishift-binary.png! > !editor-minishift-location.png! > * the widget order in the wizard is 1) Hypervisor 2) Minishift Location while in the editor it's the opposite: 1) Minishift Location 2) Hypervisor > !editor-1location-2hypervisor.png! > !wizard-1hypervisor-2location.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017