[JBoss JIRA] (JBIDE-21916) Build image function of Docker Tooling shows no message on console
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21916?page=com.atlassian.jira.plugi... ]
Xavier Coulon resolved JBIDE-21916.
-----------------------------------
Resolution: Done
reported and fixed upstream: https://bugs.eclipse.org/bugs/show_bug.cgi?id=494513
> Build image function of Docker Tooling shows no message on console
> ------------------------------------------------------------------
>
> Key: JBIDE-21916
> URL: https://issues.jboss.org/browse/JBIDE-21916
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: docker, upstream
> Affects Versions: 4.3.0.Final
> Reporter: Joseph Hwang
> Assignee: Xavier Coulon
> Fix For: 4.4.0.Alpha3
>
> Attachments: 2016-03-19_8-47-37.jpg, 2016-03-23_19-38-10.jpg
>
>
> "docker build" command show the message of build process and error on consol like below.
> {code}
> *_$ 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_*
> {code}
> But in JBossTools there is no message shown on console except progress bar.
> !2016-03-19_8-47-37.jpg!
> I recommend the 'build image function of docker tooling' to show the build message on console.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[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 closed ERT-223.
-----------------------------
Resolution: Duplicate Issue
duplicate of JBIDE-21916
> 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
> 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
[JBoss JIRA] (ERT-209) NPE when New Docker Connection dialog is open on Windows [EBZ#494521]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-209?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon resolved ERT-209.
-------------------------------
Resolution: Done
Patch reviewed and merged.
> NPE when New Docker Connection dialog is open on Windows [EBZ#494521]
> ---------------------------------------------------------------------
>
> Key: ERT-209
> URL: https://issues.jboss.org/browse/ERT-209
> Project: Eclipse Release Train
> Issue Type: Bug
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: Docker, bzira
> Fix For: Neon (4.6) RC3
>
>
> When I open the New Docker Connection, I get a NPE in the Error Log view immediately:
> java.lang.NullPointerException
> at org.eclipse.linuxtools.internal.docker.core.DefaultDockerConnectionSettingsFinder.resolveConnectionName(DefaultDockerConnectionSettingsFinder.java:144)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.resolveConnectionName(DockerConnectionManager.java:219)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.NewDockerConnectionPage.lambda$0(NewDockerConnectionPage.java:433)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalC
> There is nothing pre-filled in the dialog and an error displayed at the top saying "Provide a unique name to identify the new connection."
> I was running Eclipse Neon RC1 on Windows 10 with Docker Tooling nightly installed from here:
> http://download.eclipse.org/linuxtools/update-neon-docker-rc2
> Steps:
> 1. Install Docker Toolbox
> 2. Start Docker Machine
> 3. Start Eclipse
> 4. Open Docker Perspective
> 5. In Docker Explorer, click the link to create a new docker connection
> 6. Check your Error Log
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ERT-223) Build image function of Docker Tooling shows no message on console [EBZ#494513]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-223:
---------------------------------------
Summary: 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
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
[JBoss JIRA] (TOOLSDOC-623) Add FeedHenry Information to Existing Article about Hybrid Mobile Apps
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-623?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-623:
-------------------------------
Sprint: 2015/S8 (13-Apr > 26-Apr), 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT, 26-Oct >> 08-Nov 2015-JBDS/JBT, 09-Nov >> 22-Nov 2015-JBDS/JBT, 23-Nov >> 06-Dec 2015-JBDS/JBT, 04-Jan >> 17-Jan 2016-JBDS/JBT, 18-Jan >> 31-Jan 2016-JBDS/JBT, 01-Feb >> 14-Feb 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT, 29-Feb >> 13-Mar 2016-JBDS/JBT, 14-Mar >> 27-Mar 2016-JBDS/J 2, 28-Mar >> 10-Apr 2016-JBDS/JBT, 25-Apr >> 08-May 2016-JBDS/JBT, 09-May >> 22-May 2016-JBDS/JBT, 23-May >> 05-Jun 2016-JBDS/JBT (was: 2015/S8 (13-Apr > 26-Apr), 11-May -> 24-May 2015-JBDS/JBT, 25-May -> 07-Jun 2015-JBDS/JBT, 08-Jun -> 21-Jun 2015-JBDS/JBT, 22-Jun >> 05-Jul 2015-JBDS/JBT, 06-Jul >> 19-Jul 2015-JBDS/JBT, 20-Jul >> 02-Aug 2015-JBDS/JBT, 03-Aug >> 16-Aug 2015-JBDS/J 2, 31-Aug >> 13-Sep 2015-JBDS/JBT, 28-Sep >> 11-Oct 2015-JBDS/JBT, 12-Oct >> 25-Oct 2015-JBDS/JBT, 26-Oct >> 08-Nov 2015-JBDS/JBT, 09-Nov >> 22-Nov 2015-JBDS/JBT, 23-Nov >> 06-Dec 2015-JBDS/JBT, 04-Jan >> 17-Jan 2016-JBDS/JBT, 18-Jan >> 31-Jan 2016-JBDS/JBT, 01-Feb >> 14-Feb 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT, 29-Feb >> 13-Mar 2016-JBDS/JBT, 14-Mar >> 27-Mar 2016-JBDS/J 2, 28-Mar >> 10-Apr 2016-JBDS/JBT, 25-Apr >> 08-May 2016-JBDS/JBT, 09-May >> 22-May 2016-JBDS/JBT)
> Add FeedHenry Information to Existing Article about Hybrid Mobile Apps
> ----------------------------------------------------------------------
>
> Key: TOOLSDOC-623
> URL: https://issues.jboss.org/browse/TOOLSDOC-623
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: General documentation issues
> Reporter: Burr Sutter
> Assignee: Supriya Bharadwaj
> Fix For: 4.2.3.Final
>
>
> Originally reported by Burr here: https://issues.jboss.org/browse/JBDS-3397
> Description: https://access.redhat.com/articles/1295913
> We should add FeedHenry to this document.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (TOOLSDOC-718) Getting Started / Readme for new CDK users
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-718?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-718:
-------------------------------
Sprint: 28-Mar >> 10-Apr 2016-JBDS/JBT, 11-Apr >> 24-Apr 2016-JBDS/J 2, 09-May >> 22-May 2016-JBDS/JBT, 23-May >> 05-Jun 2016-JBDS/JBT (was: 28-Mar >> 10-Apr 2016-JBDS/JBT, 11-Apr >> 24-Apr 2016-JBDS/J 2, 09-May >> 22-May 2016-JBDS/JBT)
> Getting Started / Readme for new CDK users
> -------------------------------------------
>
> Key: TOOLSDOC-718
> URL: https://issues.jboss.org/browse/TOOLSDOC-718
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: General documentation issues
> Affects Versions: 9.1 CR1
> Reporter: Nick Boldt
> Assignee: Misha Ali
> Labels: Havoc
> Fix For: 9.1 GA
>
>
> See JBDS-3738.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years