April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4370) Windows uninstaller is not deleting "uninstaller" and "temp" and parent folders

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4370?page=com.atlassian.jira.plugin.... ] Aurélien Pupier updated JBDS-4370: ---------------------------------- Attachment: erroMessage.png > Windows uninstaller is not deleting "uninstaller" and "temp" and parent folders > ------------------------------------------------------------------------------- > > Key: JBDS-4370 > URL: https://issues.jboss.org/browse/JBDS-4370 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.AM3 > Reporter: Aurélien Pupier > Attachments: erroMessage.png, image-2017-04-24-17-25-04-048.png > > > !image-2017-04-24-17-25-04-048.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4370) Windows uninstaller is not deleting "uninstaller" and "temp" and parent folders

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBDS-4370: ------------------------------------- Summary: Windows uninstaller is not deleting "uninstaller" and "temp" and parent folders Key: JBDS-4370 URL: https://issues.jboss.org/browse/JBDS-4370 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.4.0.AM3 Reporter: Aurélien Pupier Attachments: image-2017-04-24-17-25-04-048.png !image-2017-04-24-17-25-04-048.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4369) Provide a .exe for uninstaller on Windows

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBDS-4369: ------------------------------------- Summary: Provide a .exe for uninstaller on Windows Key: JBDS-4369 URL: https://issues.jboss.org/browse/JBDS-4369 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Enhancement Components: platform-installer Affects Versions: 10.4.0.AM2 Reporter: Aurélien Pupier currently it is a .ps1 file, this is very uncommon -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24184) Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24184?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24184: ------------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24184 > URL: https://issues.jboss.org/browse/JBIDE-24184 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Fix For: 4.4.4.Final > > > to turn on/off debugging and dev_mode for an app, one needs to set env variables. The keys that are used to set the values are all defined in the docker image labels (inspectable by doing {code}docker inspect <docker-image-id>{code}: > * nodejs > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > ... > {code} > * eap > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEBUG:true", > "com.redhat.dev-mode.port": "DEBUG_PORT:8787", > ... > {code} > Our code on the other hand is hard-coding these, not reading the keys from the docker image: > {code} > public class OpenShiftDebugUtils { > private static final String DEBUG_KEY = "DEBUG"; > private static final String DEBUG_PORT_KEY = "DEBUG_PORT"; > ... > {code} > {code} > public class OpenShiftLaunchController extends AbstractSubsystemController > implements ISubsystemController, ILaunchServerController { > ... > private static final String DEV_MODE = "DEV_MODE"; //$NON-NLS-1$ > ... > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24030) Provider and plug-in name of org.boss.tools.openshift.common.core are displaying localization key

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24030?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24030: ------------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > Provider and plug-in name of org.boss.tools.openshift.common.core are displaying localization key > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-24030 > URL: https://issues.jboss.org/browse/JBIDE-24030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Priority: Optional > Fix For: 4.4.4.Final > > Attachments: image-2017-03-06-16-35-55-977.png, installed-bundles.png > > > !image-2017-03-06-16-35-55-977.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24223) CDK3 server adapter: errors on "service-manager" when starting it while cdk is already running

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24223?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24223. --------------------------------- Thanks, Andre. Closing for now. > CDK3 server adapter: errors on "service-manager" when starting it while cdk is already running > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-24223 > URL: https://issues.jboss.org/browse/JBIDE-24223 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.4.AM3 > > Attachments: image-2017-04-04-16-06-02-928.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24222) CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24222?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24222: ------------------------------------- Fix Version/s: 4.4.4.Final > CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24222 > URL: https://issues.jboss.org/browse/JBIDE-24222 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Environment: macos > xhyve supervisor > cdk3 beta3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.4.Final > > Attachments: Screenshot 2017-04-18 16.37.44.png, image-2017-04-04-15-48-59-677.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24223) CDK3 server adapter: errors on "service-manager" when starting it while cdk is already running

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24223?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-24223. -------------------------------------- Fix Version/s: 4.4.4.AM3 Resolution: Cannot Reproduce Bug > CDK3 server adapter: errors on "service-manager" when starting it while cdk is already running > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-24223 > URL: https://issues.jboss.org/browse/JBIDE-24223 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.4.AM3 > > Attachments: image-2017-04-04-16-06-02-928.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24223) CDK3 server adapter: errors on "service-manager" when starting it while cdk is already running

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24223?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24223: ------------------------------------------ weird, I can't replicate it either. Resolving as invalid. > CDK3 server adapter: errors on "service-manager" when starting it while cdk is already running > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-24223 > URL: https://issues.jboss.org/browse/JBIDE-24223 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.4.AM3 > > Attachments: image-2017-04-04-16-06-02-928.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24232) New application wizard: NPE when trying to inspect defined resources for jenkins-pipeline-example

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24232?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-24232. ------------------------------ Verified in Devstudio 10.4.0.AM3-v20170421-0111-B478. Closing. > New application wizard: NPE when trying to inspect defined resources for jenkins-pipeline-example > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-24232 > URL: https://issues.jboss.org/browse/JBIDE-24232 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3, pipeline_build > Fix For: 4.4.4.AM3, 4.5.0.AM1 > > Attachments: pipeline-buildconfig-entry.png > > > steps: > # ASSERT: use a cdk which has the "jenkins-pipeline-example" template > # EXEC: launch the app wizard and in the list of available server templates select the "jenkins-pipeline-example" template > # ASSERT: Details panel shows the details for this template and holds a button "Defined Resources..." > # EXEC: hit the "Defined Resources..." button > # ASSERT: Details dialog pops up listing all the resources > # EXEC: click the 2nd build config "BuildConfig {sample-pipeline}" > !pipeline-buildconfig-entry.png! > Result: > arrow (or +) to the left of the build config disappears, nothing else happens. In the Eclipse log you discover an NPE: > {code} > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.newapp.ResourceDetailsContentProvider.getBuildConfigChildren(ResourceDetailsContentProvider.java:93) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.ResourceDetailsContentProvider.getChildren(ResourceDetailsContentProvider.java:49) > at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1372) > at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:341) > at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:907) > at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:621) > at org.eclipse.jface.viewers.AbstractTreeViewer.lambda$0(AbstractTreeViewer.java:817) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:795) > at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:596) > at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:766) > at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1493) > at org.eclipse.jface.viewers.TreeViewer.handleTreeExpand(TreeViewer.java:882) > at org.eclipse.jface.viewers.AbstractTreeViewer$3.treeExpanded(AbstractTreeViewer.java:1505) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:133) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509) > at org.eclipse.swt.widgets.TreeItem.sendExpand(TreeItem.java:1050) > at org.eclipse.swt.widgets.Tree.expandItem_expandChildren(Tree.java:1278) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5996) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227) > at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1135) > at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2102) > at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1127) > at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2624) > at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2069) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5733) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227) > at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2140) > at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2402) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5797) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5226) > at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5375) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3703) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceListPage$13.widgetSelected(ApplicationSourceListPage.java:590) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4080) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3706) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287) > 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(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:433) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:454) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:482) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4080) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3706) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > {code} -- 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