[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
[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
[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
[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
[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