May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-226) Docker Machine preferences page causes all other Docker preference pages to be invalid [EBZ#493752]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-226: --------------------------------------- Summary: Docker Machine preferences page causes all other Docker preference pages to be invalid [EBZ#493752] Key: ERT-226 URL: https://issues.jboss.org/browse/ERT-226 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon (4.6) If a docker machine is not installed in /usr/local/bin, clicking on the Docker machine preferences page results in an error marker. Trying to click on another Docker preference page after that fails with Page Invalid error. Clearing the directories does not help. In my case, I don't have docker machine installed. It might be best to simply issue a warning instead of an error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-227) NoSuchMethodError in DockerContainerConfig.<init> [EBZ#494873]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-227: --------------------------------------- Summary: NoSuchMethodError in DockerContainerConfig.<init> [EBZ#494873] Key: ERT-227 URL: https://issues.jboss.org/browse/ERT-227 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot The following problem was reported via the automated error reporting: Message: An internal error occurred during: "Starting Containers...". java.lang.NoSuchMethodError: com.spotify.docker.client.messages.ContainerConfig.memory()Ljava/lang/Long; at org.eclipse.linuxtools.internal.docker.core.DockerContainerConfig.<init>(DockerContainerConfig.java:54) at org.eclipse.linuxtools.internal.docker.core.DockerContainerInfo.<init>(DockerContainerInfo.java:52) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getContainerInfo(DockerConnection.java:860) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.startContainer(DockerConnection.java:1275) at org.eclipse.linuxtools.internal.docker.ui.commands.StartContainersCommandHandler.executeInJob(StartContainersCommandHandler.java:44) at org.eclipse.linuxtools.internal.docker.ui.commands.BaseContainersCommandHandler$1.run(BaseContainersCommandHandler.java:57) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) The reporter(s) left the following comment(s): --- Anonymous wrote on f6fa: --- The problematic package 'com.spotify.docker.client.messages' may originate in the following bundles: com.spotify.docker.client 3.4.0.v20160225-1656, from which the following bundles present on the stack trace import it: org.eclipse.linuxtools.docker.core 1.0.0.201506101754 Bundles: | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.5.0.v20150421-2214 | | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | | org.eclipse.linuxtools.docker.core | 1.0.0.201506101754 | 1.0.0.201506101754 | | org.eclipse.linuxtools.docker.ui | 1.0.0.201506101754 | 1.0.0.201506101754 | | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 | Operating Systems: | MacOSX | 10.10.5 | 10.11.4 | The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/56bbc... for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-228) DockerException in DockerConnection.listImages [EBZ#494875]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-228: --------------------------------------- Summary: DockerException in DockerConnection.listImages [EBZ#494875] Key: ERT-228 URL: https://issues.jboss.org/browse/ERT-228 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot The following problem was reported via the automated error reporting: Message: HIDDEN org.eclipse.linuxtools.docker.core.DockerException: HIDDEN at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:949) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:922) at org.eclipse.linuxtools.internal.docker.ui.views.DockerImagesContentProvider$1$1.run(DockerImagesContentProvider.java:71) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3774) Bundles: | org.eclipse.core.jobs | 3.8.0.v20160209-0147 | 3.8.0.v20160209-0147 | | org.eclipse.linuxtools.docker.core | 2.0.0.201605161002 | 2.0.0.201605161002 | | org.eclipse.linuxtools.docker.ui | 2.0.0.201605161002 | 2.0.0.201605161002 | Operating Systems: | Windows | 6.1.0 | 6.1.0 | The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/55914... for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-229) ArrayIndexOutOfBoundsException in RunImageMainTab.initializeFrom [EBZ#494926]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-229: --------------------------------------- Summary: ArrayIndexOutOfBoundsException in RunImageMainTab.initializeFrom [EBZ#494926] Key: ERT-229 URL: https://issues.jboss.org/browse/ERT-229 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon (4.6) The following problem was reported via the automated error reporting: Message: Problems occurred when invoking code from plug-in: "org.eclipse.jface". java.lang.ArrayIndexOutOfBoundsException: 0 at org.eclipse.linuxtools.internal.docker.ui.launch.RunImageMainTab.initializeFrom(RunImageMainTab.java:502) at org.eclipse.debug.ui.AbstractLaunchConfigurationTabGroup.initializeFrom(AbstractLaunchConfigurationTabGroup.java:90) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupWrapper.initializeFrom(LaunchConfigurationTabGroupWrapper.java:201) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:766) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$8.run(LaunchConfigurationTabGroupViewer.java:637) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:654) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(LaunchConfigurationTabGroupViewer.java:615) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:590) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:960) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:573) at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:877) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:874) at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1734) at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1093) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.handleConfigurationAdded(LaunchConfigurationView.java:297) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.access$1(LaunchConfigurationView.java:286) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView$2.run(LaunchConfigurationView.java:275) 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.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | | org.eclipse.debug.ui | 3.11.101.v20160203-1230 | 3.11.101.v20160203-1230 | | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | | org.eclipse.linuxtools.docker.ui | 1.2.2.201603181907 | 1.2.2.201603181907 | | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 | Operating Systems: | MacOSX | 10.11.3 | 10.11.3 | The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/572a0... for the latest data. Thank you for your assistance. Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22367) Create and use Neon.0.RC target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22367?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22367: ------------------------------- Summary: Create and use Neon.0.RC target platform (was: Create and use Neon.0.RC3/4 target platform) > Create and use Neon.0.RC target platform > ---------------------------------------- > > Key: JBIDE-22367 > URL: https://issues.jboss.org/browse/JBIDE-22367 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha3 > > > Prepare TP to use Neon.0.RC3 or RC4 bits, which will be available June 3 0r 10. Cloned from JBIDE-22200. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build; > * update install/matrix jobs to use new Eclipse JEE/platform binary; > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22467) Include Docker tooling 2.0.0.RC3

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-22467: ------------------------------------- Summary: Include Docker tooling 2.0.0.RC3 Key: JBIDE-22467 URL: https://issues.jboss.org/browse/JBIDE-22467 Project: Tools (JBoss Tools) Issue Type: Task Components: target-platform Affects Versions: 4.4.0.Alpha2 Reporter: Xavier Coulon Include the Docker tooling 2.0.0.RC3 once it is available (link to update site will be posted here). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22465) npm, bower not recognized as an internal or external command on windows

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22465?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22465: ------------------------------------- I have tested bower / npm against nvm installation on Windows 7 and everything works just fine. is it Windows 10 specific ? > npm, bower not recognized as an internal or external command on windows > ----------------------------------------------------------------------- > > Key: JBIDE-22465 > URL: https://issues.jboss.org/browse/JBIDE-22465 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: nodejs > Affects Versions: 4.4.0.Alpha3 > Reporter: Pavol Srna > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.4.0.Alpha3 > > Attachments: bower.png, cmd.png, npm.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

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

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-152?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon resolved ERT-152. ------------------------------- Resolution: Done > 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 > Assignee: Xavier Coulon > Labels: 4.2.1, Docker, bzira > Fix For: Neon.1 (4.6) > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3913) EAP 7 shell scripts have changes since EAP 6.4; need to update devstudio installer accordingly

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3913?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3913: ------------------------------------- I tried this in devstudio-10.0.0.Alpha3-v20160531-1024-B5476-installer-eap.jar . After installation, EAP 7 was set up automatically and it then started correctly. > EAP 7 shell scripts have changes since EAP 6.4; need to update devstudio installer accordingly > ---------------------------------------------------------------------------------------------- > > Key: JBDS-3913 > URL: https://issues.jboss.org/browse/JBDS-3913 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: installer > Environment: http://www.qa.jboss.com/binaries/RHDS/10.0/snapshots/builds/devstudio.pro... > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.Alpha3 > > Attachments: 1.png, 2.png > > > See attached screenshots -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ] Martin Malina commented on ERT-204: ----------------------------------- I tried this today and it still doesn't work. The search button does find my docker machine and I can select it. It then correctly fills in the name and IP, but it does not check the authentication checkbox and so there is no cert path configured and it doesn't work. > Docker Machine lookup does not work on Windows machines [EBZ#494305] > -------------------------------------------------------------------- > > Key: ERT-204 > URL: https://issues.jboss.org/browse/ERT-204 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 May 2016