[JBoss JIRA] (JBTIS-719) Fix 'DataTransformationDeploymentEAPTest'
by Tomáš Sedmík (JIRA)
[ https://issues.jboss.org/browse/JBTIS-719?page=com.atlassian.jira.plugin.... ]
Tomáš Sedmík edited comment on JBTIS-719 at 6/1/16 4:47 AM:
------------------------------------------------------------
(x)
On Mac only:
{code}
Timeout after: 300 s.: server's state is: Started
{code}
--> set runtime JRE (JavaSE-1.6 is set as default)
was (Author: tsedmik):
On Mac only:
{code}
Timeout after: 300 s.: server's state is: Started
{code}
--> set runtime JRE (JavaSE-1.6 is set as default)
> Fix 'DataTransformationDeploymentEAPTest'
> -----------------------------------------
>
> Key: JBTIS-719
> URL: https://issues.jboss.org/browse/JBTIS-719
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE, QE
> Affects Versions: 4.3.0.Final
> Environment: Fuse on EAP 6.3.0.ER1
> JBDS 9.1.0.GA
> JBDSIS 9.0.0.GA
> Reporter: Tomáš Sedmík
> Assignee: Tomáš Sedmík
> Fix For: 4.3.0.Final
>
>
> Fuse on EAP log was slightly changed.
> {code}
> ...file://src/data) Creating JAXBContext...
> {code}
> to
> {code}
> ...file://src/data) Created XMLInputFactory...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBTIS-719) Fix 'DataTransformationDeploymentEAPTest'
by Tomáš Sedmík (JIRA)
[ https://issues.jboss.org/browse/JBTIS-719?page=com.atlassian.jira.plugin.... ]
Tomáš Sedmík edited comment on JBTIS-719 at 6/1/16 4:45 AM:
------------------------------------------------------------
{code}
Timeout after: 10 s.: console contains '(CamelContext: spring-context) started'
{code}
{code}
at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:173)
at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:126)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:91)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:61)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:46)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:34)
at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:25)
at org.jboss.tools.fuse.ui.bot.test.DeploymentEAPTest.testDeployment(DeploymentEAPTest.java:88)
{code}
--> a bug: see https://issues.jboss.org/browse/FUSETOOLS-1866
was (Author: tsedmik):
{code}
Timeout after: 10 s.: console contains '(CamelContext: spring-context) started'
{code}
{code}
at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:173)
at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:126)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:91)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:61)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:46)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:34)
at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:25)
at org.jboss.tools.fuse.ui.bot.test.DeploymentEAPTest.testDeployment(DeploymentEAPTest.java:88)
{code}
> Fix 'DataTransformationDeploymentEAPTest'
> -----------------------------------------
>
> Key: JBTIS-719
> URL: https://issues.jboss.org/browse/JBTIS-719
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE, QE
> Affects Versions: 4.3.0.Final
> Environment: Fuse on EAP 6.3.0.ER1
> JBDS 9.1.0.GA
> JBDSIS 9.0.0.GA
> Reporter: Tomáš Sedmík
> Assignee: Tomáš Sedmík
> Fix For: 4.3.0.Final
>
>
> Fuse on EAP log was slightly changed.
> {code}
> ...file://src/data) Creating JAXBContext...
> {code}
> to
> {code}
> ...file://src/data) Created XMLInputFactory...
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-22279) Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22279?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-22279.
-------------------------------
Verified with DS 10.0.0.Alpha3 B5485 / central TP 4.60.0.Alpha1-SNAPSHOT
> Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22279
> URL: https://issues.jboss.org/browse/JBIDE-22279
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central-update, target-platform, upstream
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.4.0.Alpha2
>
> Attachments: jbide22279.png
>
>
> Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed:
> {code} Software being installed: Mylyn Context Connector: Plug-in Development 3.18.0.v20151013-1847 (org.eclipse.mylyn.pde_feature.feature.group 3.18.0.v20151013-1847)
> Software currently installed: Mylyn Context Connector: Java Development 3.19.0.v20160111-2059 (org.eclipse.mylyn.java_feature.feature.group 3.19.0.v20160111-2059)
> {code}
> Opening this issue just as a reminder to check that we're using the same version of Neon/Mylyn in Central & TP so we don't hit this problem again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21203) two different incompatible versions of org.eclipse.mylyn.context_feature in JBT/JBDS vs Central TPs
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21203?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-21203.
-------------------------------
Closing as duplicate since the original is already verified/closed.
> two different incompatible versions of org.eclipse.mylyn.context_feature in JBT/JBDS vs Central TPs
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21203
> URL: https://issues.jboss.org/browse/JBIDE-21203
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
>
> {code}
> [p2.dir] Cannot complete the install because one or more required items could not be found.
> [p2.dir] Software being installed: Mylyn Context Connector: Java Development 3.17.0.v20150828-2014 (org.eclipse.mylyn.java_feature.feature.group 3.17.0.v20150828-2014)
> [p2.dir] Missing requirement: Mylyn Task-Focused Interface 3.17.0.v20150625-2044 (org.eclipse.mylyn.context_feature.feature.group 3.17.0.v20150625-2044) requires 'org.eclipse.mylyn_feature.feature.group [3.17.0,3.18.0)' but it could not be found
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: Mylyn Context Connector: Java Development 3.17.0.v20150828-2014 (org.eclipse.mylyn.java_feature.feature.group 3.17.0.v20150828-2014)
> [p2.dir] To: org.eclipse.mylyn.context_feature.feature.group [3.17.0,3.18.0)
> [p2.dir] Application failed, log file location: /mnt/hudson_workspace/workspace/jbosstools-composite-install_master/eclipse/configuration/1449545575243.log
> [p2.dir]
> [p2.dir] !ENTRY org.eclipse.equinox.p2.director 4 10053 2015-12-07 22:34:28.175
> [p2.dir] !MESSAGE Cannot complete the install because one or more required items could not be found.
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2015-12-07 22:34:28.175
> [p2.dir] !MESSAGE Software being installed: Mylyn Context Connector: Java Development 3.17.0.v20150828-2014 (org.eclipse.mylyn.java_feature.feature.group 3.17.0.v20150828-2014)
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2015-12-07 22:34:28.175
> [p2.dir] !MESSAGE Missing requirement: Mylyn Task-Focused Interface 3.17.0.v20150625-2044 (org.eclipse.mylyn.context_feature.feature.group 3.17.0.v20150625-2044) requires 'org.eclipse.mylyn_feature.feature.group [3.17.0,3.18.0)' but it could not be found
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2015-12-07 22:34:28.175
> [p2.dir] !MESSAGE Cannot satisfy dependency:
> [p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-12-07 22:34:28.175
> [p2.dir] !MESSAGE From: Mylyn Context Connector: Java Development 3.17.0.v20150828-2014 (org.eclipse.mylyn.java_feature.feature.group 3.17.0.v20150828-2014)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-227) NoSuchMethodError in DockerContainerConfig.<init> [EBZ#494873]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-227?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon resolved ERT-227.
-------------------------------
Resolution: Done
> 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
> Assignee: Roland Grunberg
> Labels: Docker, bzira
>
> 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)
10 years, 1 month
[JBoss JIRA] (ERT-223) Build image function of Docker Tooling shows no message on console [EBZ#494513]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-223?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon resolved ERT-223.
-------------------------------
Resolution: Done
Patch reviewed and merged
> Build image function of Docker Tooling shows no message on console [EBZ#494513]
> -------------------------------------------------------------------------------
>
> Key: ERT-223
> URL: https://issues.jboss.org/browse/ERT-223
> 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)
>
>
> Bug initially reported in https://issues.jboss.org/browse/JBIDE-21916
> ----
> "docker build" command show the message of build process and error on consol like below.
> *_$ docker build --tag=jboss/wildfly:joseph .
> Sending build context to Docker daemon 1.021 MB
> Step 1 : FROM jboss/wildfly
> ---> bda4b726bee1
> Step 2 : MAINTAINER Joseph Hwang "gladitor67(a)naver.com"
> ---> Using cache
> ---> 8914ffd24e28
> Step 3 : ENV WILDFLY_VERSION 10.0.0.Final
> ---> Using cache
> ---> 176b7b9a5b7f
> Step 4 : ENV JBOSS_HOME /opt/jboss/wildfly
> ---> Using cache
> ---> 3f8d1e30f787
> Step 5 : RUN cd $HOME && curl -O https://download.jboss.org/wildfly/$WILDFLY_VERSION/wildfly-$WILDFLY_VERS... && unzip wildfly-$WILDFLY_VERSION.zip && mv $HOME/wildfly-$WILDFLY_VERSION $JBOSS_HOME && rm wildfly-$WILDFLY_VERSION.zip
> ---> Using cache
> ---> 454f6749ff6c
> Step 6 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql
> ---> Using cache
> ---> 2fce5a99913c
> Step 7 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql/main
> ---> Using cache
> ---> 1e4f8bd9aa50
> Step 8 : ADD module.xml $JBOSS_HOME/modules/system/layers/base/com/mysql/main/
> ---> Using cache
> ---> 723e4a09b3a0
> Step 9 : ADD mysql-connector-java-5.1.38-bin.jar $JBOSS_HOME/modules/system/layers/base/com/mysql/main/
> ---> Using cache
> ---> 7cc730359445
> Step 10 : ADD standalone.xml $JBOSS_HOME/standalone/configuration/
> ---> Using cache
> ---> 9ac873838925
> Successfully built 79d34c841245_*
> But in JBossTools there is no message shown on console except progress bar.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-223) Build image function of Docker Tooling shows no message on console [EBZ#494513]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-223?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon updated ERT-223:
------------------------------
Sprint: devex #115 May 2016
> Build image function of Docker Tooling shows no message on console [EBZ#494513]
> -------------------------------------------------------------------------------
>
> Key: ERT-223
> URL: https://issues.jboss.org/browse/ERT-223
> 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)
>
>
> Bug initially reported in https://issues.jboss.org/browse/JBIDE-21916
> ----
> "docker build" command show the message of build process and error on consol like below.
> *_$ docker build --tag=jboss/wildfly:joseph .
> Sending build context to Docker daemon 1.021 MB
> Step 1 : FROM jboss/wildfly
> ---> bda4b726bee1
> Step 2 : MAINTAINER Joseph Hwang "gladitor67(a)naver.com"
> ---> Using cache
> ---> 8914ffd24e28
> Step 3 : ENV WILDFLY_VERSION 10.0.0.Final
> ---> Using cache
> ---> 176b7b9a5b7f
> Step 4 : ENV JBOSS_HOME /opt/jboss/wildfly
> ---> Using cache
> ---> 3f8d1e30f787
> Step 5 : RUN cd $HOME && curl -O https://download.jboss.org/wildfly/$WILDFLY_VERSION/wildfly-$WILDFLY_VERS... && unzip wildfly-$WILDFLY_VERSION.zip && mv $HOME/wildfly-$WILDFLY_VERSION $JBOSS_HOME && rm wildfly-$WILDFLY_VERSION.zip
> ---> Using cache
> ---> 454f6749ff6c
> Step 6 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql
> ---> Using cache
> ---> 2fce5a99913c
> Step 7 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql/main
> ---> Using cache
> ---> 1e4f8bd9aa50
> Step 8 : ADD module.xml $JBOSS_HOME/modules/system/layers/base/com/mysql/main/
> ---> Using cache
> ---> 723e4a09b3a0
> Step 9 : ADD mysql-connector-java-5.1.38-bin.jar $JBOSS_HOME/modules/system/layers/base/com/mysql/main/
> ---> Using cache
> ---> 7cc730359445
> Step 10 : ADD standalone.xml $JBOSS_HOME/standalone/configuration/
> ---> Using cache
> ---> 9ac873838925
> Successfully built 79d34c841245_*
> But in JBossTools there is no message shown on console except progress bar.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-223) Build image function of Docker Tooling shows no message on console [EBZ#494513]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-223?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon reassigned ERT-223:
---------------------------------
Resolution: (was: Duplicate Issue)
Assignee: Xavier Coulon
> Build image function of Docker Tooling shows no message on console [EBZ#494513]
> -------------------------------------------------------------------------------
>
> Key: ERT-223
> URL: https://issues.jboss.org/browse/ERT-223
> 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)
>
>
> Bug initially reported in https://issues.jboss.org/browse/JBIDE-21916
> ----
> "docker build" command show the message of build process and error on consol like below.
> *_$ docker build --tag=jboss/wildfly:joseph .
> Sending build context to Docker daemon 1.021 MB
> Step 1 : FROM jboss/wildfly
> ---> bda4b726bee1
> Step 2 : MAINTAINER Joseph Hwang "gladitor67(a)naver.com"
> ---> Using cache
> ---> 8914ffd24e28
> Step 3 : ENV WILDFLY_VERSION 10.0.0.Final
> ---> Using cache
> ---> 176b7b9a5b7f
> Step 4 : ENV JBOSS_HOME /opt/jboss/wildfly
> ---> Using cache
> ---> 3f8d1e30f787
> Step 5 : RUN cd $HOME && curl -O https://download.jboss.org/wildfly/$WILDFLY_VERSION/wildfly-$WILDFLY_VERS... && unzip wildfly-$WILDFLY_VERSION.zip && mv $HOME/wildfly-$WILDFLY_VERSION $JBOSS_HOME && rm wildfly-$WILDFLY_VERSION.zip
> ---> Using cache
> ---> 454f6749ff6c
> Step 6 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql
> ---> Using cache
> ---> 2fce5a99913c
> Step 7 : RUN mkdir $JBOSS_HOME/modules/system/layers/base/com/mysql/main
> ---> Using cache
> ---> 1e4f8bd9aa50
> Step 8 : ADD module.xml $JBOSS_HOME/modules/system/layers/base/com/mysql/main/
> ---> Using cache
> ---> 723e4a09b3a0
> Step 9 : ADD mysql-connector-java-5.1.38-bin.jar $JBOSS_HOME/modules/system/layers/base/com/mysql/main/
> ---> Using cache
> ---> 7cc730359445
> Step 10 : ADD standalone.xml $JBOSS_HOME/standalone/configuration/
> ---> Using cache
> ---> 9ac873838925
> Successfully built 79d34c841245_*
> But in JBossTools there is no message shown on console except progress bar.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ERT-225) NullPointerException in DockerImagesContentProvider.getElements [EBZ#494872]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-225?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon resolved ERT-225.
-------------------------------
Resolution: Done
> NullPointerException in DockerImagesContentProvider.getElements [EBZ#494872]
> ----------------------------------------------------------------------------
>
> Key: ERT-225
> URL: https://issues.jboss.org/browse/ERT-225
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: Docker, bzira
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> java.lang.NullPointerException: null
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerImagesContentProvider.getElements(DockerImagesContentProvider.java:49)
> at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1000)
> at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:700)
> at org.eclipse.jface.viewers.AbstractTableViewer.getRawChildren(AbstractTableViewer.java:1043)
> at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:906)
> at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:1083)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:667)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:615)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:607)
> at org.eclipse.jface.viewers.StructuredViewer$7.run(StructuredViewer.java:1526)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1462)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1423)
> at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1523)
> at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:522)
> at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1482)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerImagesContentProvider$1$1.run(DockerImagesContentProvider.java:72)
> 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:4155)
> Bundles:
> | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 |
> | org.eclipse.linuxtools.docker.ui | 1.2.1.201602162146 | 1.2.1.201602162146 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/57469... 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)
10 years, 1 month