April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-150) Offer possibility to remove container with same name during a new run [EBZ#482986]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-150: --------------------------------------- Summary: Offer possibility to remove container with same name during a new run [EBZ#482986] Key: ERT-150 URL: https://issues.jboss.org/browse/ERT-150 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot If a container with the same name already exists, the "Run Image" wizard does not allow the completion. An alternative approach would be to raise a warning and prompt the user to kill and remove the old container with the same name before creating the new one. This allows for faster container cycles when the user wants to keep the same name for his containers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-152) Restore dialog when building Docker image if connection does not exist anymore [EBZ#484485]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-152: --------------------------------------- Summary: Restore dialog when building Docker image if connection does not exist anymore [EBZ#484485] Key: ERT-152 URL: https://issues.jboss.org/browse/ERT-152 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Mars.2 (4.5) Otherwise, the tooling fails with the following error: "No Docker connection named 'xyz' exists." and the only workaround is to remove the associated launch configuration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-151) Data Volume Container do not need a container path [EBZ#483012]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-151: --------------------------------------- Summary: Data Volume Container do not need a container path [EBZ#483012] Key: ERT-151 URL: https://issues.jboss.org/browse/ERT-151 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon (4.6) The dialog to specify the volumes for a container to run is wrong, because data volume containers are not mounted on a user-given container path but instead, the selected container will mount its own defined volume. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-153) StandInException in DockerConnection$LogThread.execute [EBZ#485737]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-153: --------------------------------------- Summary: StandInException in DockerConnection$LogThread.execute [EBZ#485737] Key: ERT-153 URL: https://issues.jboss.org/browse/ERT-153 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot The following incident was reported via the automated error reporting: The user(s) left the following comments: --- wrote: --- shutting down a wildfly instance (takes a couple seconds) on docker 1.7.1. Not really a bug in my opinion, operation went as expected. code: 4 plugin: org.eclipse.linuxtools.docker.core_1.0.0.201506102203 message: sleep interrupted fingerprint: 18dade7c exception class: org.eclipse.epp.internal.logging.aeri.ui.log.StandInStacktraceProvider$StandInException exception message: Stand-In Stacktrace supplied by the Eclipse Error Reporting number of children: 0 org.eclipse.epp.internal.logging.aeri.ui.log.StandInStacktraceProvider$StandInException: Stand-In Stacktrace supplied by the Eclipse Error Reporting at org.eclipse.linuxtools.docker.core.Activator.log(Activator.java:52) at org.eclipse.linuxtools.docker.core.Activator.logErrorMessage(Activator.java:56) at org.eclipse.linuxtools.internal.docker.core.DockerConnection$LogThread.execute(DockerConnection.java:798)[REQUIRED, TOPMOST] at org.eclipse.linuxtools.internal.docker.core.AbstractKillableThread.run(AbstractKillableThread.java:49) General Information: reported-by: anonymous-id: 824b7eb7-45b7-49fc-a1e5-a94fcf50da7e eclipse-build-id: 4.5.0.I20150603-2000 eclipse-product: org.eclipse.epp.package.jee.product operating system: Linux 3.19.0 (x86_64) - gtk jre-version: 1.8.0_51-b16 The following plug-ins were present on the execution stack (*): 1. org.eclipse.linuxtools.docker.core_1.0.0.201506102203 Please note that: * Messages, stacktraces, and nested status objects may be shortened. * Bug fields like status, resolution, and whiteboard are sent back to reporters. * The list of present bundles and their respective versions was calculated by package naming heuristics. This may or may not reflect reality. Other Resources: * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/55ca39... * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide Thank you for your assistance. Your friendly error-reports-inbox. This bug was created on behalf of xcoulon@xxxxxxxxxxxx. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-146) Upgrade to Spotify client 3.6.4 [EBZ#492235]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-146: --------------------------------------- Summary: Upgrade to Spotify client 3.6.4 [EBZ#492235] Key: ERT-146 URL: https://issues.jboss.org/browse/ERT-146 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot CQ was approved http://dev.eclipse.org/ipzilla/show_bug.cgi?id=11108, but third-party dependencies need to be added/upgraded into Eclipse Orbit, too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22151) Failed to install JBT in Eclipse

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22151?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22151. --------------------------------- > Failed to install JBT in Eclipse > -------------------------------- > > Key: JBIDE-22151 > URL: https://issues.jboss.org/browse/JBIDE-22151 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.0.Alpha1 > Environment: Operating System: have tried Fedora 17 and 22 > jbt version: 3.2.0.Alpha1-v20160409-1043-B1241 > eclipse: > Version: Neon Milestone 6 (4.6.0M6) > Build id: 20160329-0659 > Reporter: Chunyun Chen > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > Attachments: jbt44alpha1-os3-1.png, jbt44alpha1-os3.png, jbt_installation_1.png, jbt_installation_2.png > > > Will meet below dependency errors when installing jbt in eclipse: > " > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.feature.feature.group 3.2.0.Alpha1-v20160409-1043-B1241) > Missing requirement: Openshift 3 Client 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.client 3.2.0.Alpha1-v20160409-1043-B1241) requires 'bundle org.eclipse.jetty.websocket.client 9.2.13' but it could not be found > Cannot satisfy dependency: > From: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160409-1043-B1241 (org.jboss.tools.openshift.feature.feature.group 3.2.0.Alpha1-v20160409-1043-B1241) > To: org.jboss.tools.openshift.client [3.2.0.Alpha1-v20160409-1043-B1241] > " -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22156) NPE is thrown when no template parameter is selected and reset button is clicked

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22156?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22156. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5207. > NPE is thrown when no template parameter is selected and reset button is clicked > -------------------------------------------------------------------------------- > > Key: JBIDE-22156 > URL: https://issues.jboss.org/browse/JBIDE-22156 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: application_wizard, openshift_v3, respin-b > Fix For: 4.4.0.Alpha1 > > > When a Reset button, to reset a template parameter, on second New OpenShift Application wizard page is clicked and there is no selection, following error pops up in error log > {code} > Unhandled event loop exception > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.resetParameter(NewApplicationWizardModel.java:287) > at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateParametersPage$7.widgetSelected(TemplateParametersPage.java:383) > 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:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > 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: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.GeneratedMethodAccessor81.invoke(Unknown Source) > 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:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) > 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:493) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > 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:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > 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:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22161) Resize of wizard Deploy Image to OpenShift breaks layout

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22161?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22161. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5207. > Resize of wizard Deploy Image to OpenShift breaks layout > -------------------------------------------------------- > > Key: JBIDE-22161 > URL: https://issues.jboss.org/browse/JBIDE-22161 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: after.png, before.png > > > Attempt to resize wizard page Deployment configuration and scalability in Deploy Image to OpenShift wizard break layout. See following screenshots before and after. > !before.png! > !after.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21786) Change "Learn about JBoss" link?

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21786?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-21786. ------------------------------ Verified in JBDS 10.0.0.Alpha1-v20160422-0424-B5207. Closing. > Change "Learn about JBoss" link? > -------------------------------- > > Key: JBIDE-21786 > URL: https://issues.jboss.org/browse/JBIDE-21786 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Central has a "Learn about JBoss" link (http://screencast.com/t/rnUDVvKW3Zsq @ 0'11") that opens http://www.jboss.org/get-started/. Does it need to point to something else? If yes then what? > cc [~crobson], [~maxandersen], [~rayploski-launch] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21187) Fix issues with styled label providers

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21187?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21187: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/785, https://github.com/jbosstools/jbosstools-openshift/pull/1121 (was: https://github.com/jbosstools/jbosstools-openshift/pull/785, https://github.com/jbosstools/jbosstools-openshift/pull/838) > Fix issues with styled label providers > -------------------------------------- > > Key: JBIDE-21187 > URL: https://issues.jboss.org/browse/JBIDE-21187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Snjezana Peco > Assignee: Andre Dietisheim > Labels: new_and_noteworthy > Fix For: 4.4.x > > Attachments: bad-labels-tree.png, correct-labels-tree.png, openshift2-grey-decorations.png, openshift3-grey-decorations.png > > > Since https://bugs.eclipse.org/bugs/show_bug.cgi?id=466499 has been fixed, we can remove the workaround related to styled label providers. > The fix is included in Mars 4.5.1 (Mars.1) and Neon 4.6.0M2. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016