[JBoss JIRA] (JBIDE-21916) Build image function of Docker Tooling shows no message on console
by Joseph Hwang (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21916?page=com.atlassian.jira.plugi... ]
Joseph Hwang edited comment on JBIDE-21916 at 3/23/16 6:58 AM:
---------------------------------------------------------------
For your information, my docker os is windows 10, so the directory seperator is \, not /. However we have no problem in creating docker building image with eclipse docker tooling.
And I attach the dialog which shows the error message of docker build. The console view of Eclipse IDE shows nothing, but shows the dialog which contains the error message.
!!!C:\Users\joseph\Desktop\2016-03-23_19-38-10.jpg|thumbnail!!!
was (Author: aupres):
For your information, my docker os is windows 10, so the directory seperator is \, not /. However we have no problem in creating docker building image with eclipse docker tooling.
And I attach the dialog which shows the error message of docker build. The console view of Eclipse IDE shows nothing, but shows the dialog which contains the error message.
!!!C:\Users\joseph\Desktop\2016-03-23_19-38-10.jpg|thumbnail!!
> 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.Alpha1
>
> Attachments: 2016-03-19_8-47-37.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] (JBIDE-21916) Build image function of Docker Tooling shows no message on console
by Joseph Hwang (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21916?page=com.atlassian.jira.plugi... ]
Joseph Hwang edited comment on JBIDE-21916 at 3/23/16 6:58 AM:
---------------------------------------------------------------
For your information, my docker os is windows 10, so the directory seperator is \, not /. However we have no problem in creating docker building image with eclipse docker tooling.
And I attach the dialog which shows the error message of docker build. The console view of Eclipse IDE shows nothing, but shows the dialog which contains the error message.
!!!2016-03-23_19-38-10.jpg|thumbnail!!!
was (Author: aupres):
For your information, my docker os is windows 10, so the directory seperator is \, not /. However we have no problem in creating docker building image with eclipse docker tooling.
And I attach the dialog which shows the error message of docker build. The console view of Eclipse IDE shows nothing, but shows the dialog which contains the error message.
!!!C:\Users\joseph\Desktop\2016-03-23_19-38-10.jpg|thumbnail!!!
> 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.Alpha1
>
> Attachments: 2016-03-19_8-47-37.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] (JBIDE-21916) Build image function of Docker Tooling shows no message on console
by Joseph Hwang (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21916?page=com.atlassian.jira.plugi... ]
Joseph Hwang edited comment on JBIDE-21916 at 3/23/16 6:58 AM:
---------------------------------------------------------------
For your information, my docker os is windows 10, so the directory seperator is \, not /. However we have no problem in creating docker building image with eclipse docker tooling.
And I attach the dialog which shows the error message of docker build. The console view of Eclipse IDE shows nothing, but shows the dialog which contains the error message.
!!!C:\Users\joseph\Desktop\2016-03-23_19-38-10.jpg|thumbnail!!
was (Author: aupres):
For your information, my docker os is windows 10, so the directory seperator is \, not /. However we have no problem in creating docker building image with eclipse docker tooling.
And I attach the dialog which shows the error message of docker build. The console view of Eclipse IDE shows nothing, but shows the dialog which contains the error message.
!C:\Users\joseph\Desktop\2016-03-23_19-38-10.jpg!
> 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.Alpha1
>
> Attachments: 2016-03-19_8-47-37.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] (JBIDE-21916) Build image function of Docker Tooling shows no message on console
by Joseph Hwang (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21916?page=com.atlassian.jira.plugi... ]
Joseph Hwang edited comment on JBIDE-21916 at 3/23/16 6:55 AM:
---------------------------------------------------------------
For your information, my docker os is windows 10, so the directory seperator is \, not /. However we have no problem in creating docker building image with eclipse docker tooling.
And I attach the dialog which shows the error message of docker build. The console view of Eclipse IDE shows nothing, but shows the dialog which contains the error message.
[!C:\Users\joseph\Desktop\2016-03-23_19-38-10.jpg!]
was (Author: aupres):
For your information, my docker os is windows 10, so the directory seperator is \, not /. However we have no problem in creating docker building image with eclipse docker tooling.
And I attach the dialog which shows the error message of docker build. The console view of Eclipse IDE shows nothing, but shows the dialog which contains the error message.
C:\Users\joseph\Desktop\2016-03-23_19-38-10.jpg
> 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.Alpha1
>
> Attachments: 2016-03-19_8-47-37.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] (JBIDE-21916) Build image function of Docker Tooling shows no message on console
by Joseph Hwang (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21916?page=com.atlassian.jira.plugi... ]
Joseph Hwang edited comment on JBIDE-21916 at 3/23/16 6:56 AM:
---------------------------------------------------------------
For your information, my docker os is windows 10, so the directory seperator is \, not /. However we have no problem in creating docker building image with eclipse docker tooling.
And I attach the dialog which shows the error message of docker build. The console view of Eclipse IDE shows nothing, but shows the dialog which contains the error message.
!C:\Users\joseph\Desktop\2016-03-23_19-38-10.jpg!
was (Author: aupres):
For your information, my docker os is windows 10, so the directory seperator is \, not /. However we have no problem in creating docker building image with eclipse docker tooling.
And I attach the dialog which shows the error message of docker build. The console view of Eclipse IDE shows nothing, but shows the dialog which contains the error message.
[!C:\Users\joseph\Desktop\2016-03-23_19-38-10.jpg!]
> 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.Alpha1
>
> Attachments: 2016-03-19_8-47-37.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] (JBIDE-21916) Build image function of Docker Tooling shows no message on console
by Joseph Hwang (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21916?page=com.atlassian.jira.plugi... ]
Joseph Hwang edited comment on JBIDE-21916 at 3/23/16 6:54 AM:
---------------------------------------------------------------
For your information, my docker os is windows 10, so the directory seperator is \, not /. However we have no problem in creating docker building image with eclipse docker tooling.
And I attach the dialog which shows the error message of docker build. The console view of Eclipse IDE shows nothing, but shows the dialog which contains the error message.
C:\Users\joseph\Desktop\2016-03-23_19-38-10.jpg
was (Author: aupres):
For your information, my docker os is windows 10, so the directory seperator is \, not /. However we have no problem in creating docker building image with eclipse docker tooling.
And I attach the dialog which shows the error message of docker build. The console view of Eclipse IDE shows nothing, but shows the dialog which contains the error message.
!C:\Users\joseph\Desktop\2016-03-23_19-38-10.jpg!
> 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.Alpha1
>
> Attachments: 2016-03-19_8-47-37.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] (JBIDE-21916) Build image function of Docker Tooling shows no message on console
by Joseph Hwang (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21916?page=com.atlassian.jira.plugi... ]
Joseph Hwang edited comment on JBIDE-21916 at 3/23/16 6:53 AM:
---------------------------------------------------------------
For your information, my docker os is windows 10, so the directory seperator is \, not /. However we have no problem in creating docker building image with eclipse docker tooling.
And I attach the dialog which shows the error message of docker build. The console view of Eclipse IDE shows nothing, but shows the dialog which contains the error message.
!C:\Users\joseph\Desktop\2016-03-23_19-38-10.jpg!
was (Author: aupres):
For your information, my docker os is windows 10, so the directory seperator is \, not /. However we have no problem in creating docker building image with eclipse docker tooling.
And I attach the dialog which shows the error message of docker build. The console view of Eclipse IDE shows nothing, but shows the dialog which contains the error message.
!C:\Users\joseph\Desktop\2016-03-23_19-38-10.jpg!
> 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.Alpha1
>
> Attachments: 2016-03-19_8-47-37.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] (JBIDE-21916) Build image function of Docker Tooling shows no message on console
by Joseph Hwang (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21916?page=com.atlassian.jira.plugi... ]
Joseph Hwang commented on JBIDE-21916:
--------------------------------------
For your information, my docker os is windows 10, so the directory seperator is \, not /. However we have no problem in creating docker building image with eclipse docker tooling.
And I attach the dialog which shows the error message of docker build. The console view of Eclipse IDE shows nothing, but shows the dialog which contains the error message.
!C:\Users\joseph\Desktop\2016-03-23_19-38-10.jpg!
> 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.Alpha1
>
> Attachments: 2016-03-19_8-47-37.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] (JBIDE-21948) Error is shown when selecting Build Config tabbed property in Properties view
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21948:
-------------------------------------
Summary: Error is shown when selecting Build Config tabbed property in Properties view
Key: JBIDE-21948
URL: https://issues.jboss.org/browse/JBIDE-21948
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Priority: Critical
When I am trying to display properties for a build config of an OpenShift 3 application, error is shown with following stack trace:
{code}
java.lang.ClassCastException: com.openshift.internal.restclient.model.build.SourceBuildStrategy cannot be cast to com.openshift.restclient.model.build.ISTIBuildStrategy
at org.jboss.tools.openshift.internal.ui.property.BuildConfigPropertySource.getPropertyValue(BuildConfigPropertySource.java:106)
at org.eclipse.ui.views.properties.PropertySheetEntry.refreshValues(PropertySheetEntry.java:590)
at org.eclipse.ui.views.properties.PropertySheetEntry.refreshChildEntries(PropertySheetEntry.java:547)
at org.eclipse.ui.views.properties.PropertySheetEntry.setValues(PropertySheetEntry.java:736)
at org.eclipse.ui.views.properties.PropertySheetViewer.setInput(PropertySheetViewer.java:986)
at org.eclipse.ui.views.properties.PropertySheetPage.selectionChanged(PropertySheetPage.java:518)
at org.jboss.tools.openshift.internal.ui.property.tabbed.OpenShiftResourcePropertySection$2.selectionChanged(OpenShiftResourcePropertySection.java:135)
at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163)
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.Viewer.fireSelectionChanged(Viewer.java:160)
at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197)
at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257)
at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242)
at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408)
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)
10 years
[JBoss JIRA] (JBIDE-21948) Error is shown when selecting Build Config tabbed property in Properties view
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21948?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21948:
----------------------------------
Labels: openshift_v3 properties (was: )
> Error is shown when selecting Build Config tabbed property in Properties view
> -----------------------------------------------------------------------------
>
> Key: JBIDE-21948
> URL: https://issues.jboss.org/browse/JBIDE-21948
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, properties
>
> When I am trying to display properties for a build config of an OpenShift 3 application, error is shown with following stack trace:
> {code}
> java.lang.ClassCastException: com.openshift.internal.restclient.model.build.SourceBuildStrategy cannot be cast to com.openshift.restclient.model.build.ISTIBuildStrategy
> at org.jboss.tools.openshift.internal.ui.property.BuildConfigPropertySource.getPropertyValue(BuildConfigPropertySource.java:106)
> at org.eclipse.ui.views.properties.PropertySheetEntry.refreshValues(PropertySheetEntry.java:590)
> at org.eclipse.ui.views.properties.PropertySheetEntry.refreshChildEntries(PropertySheetEntry.java:547)
> at org.eclipse.ui.views.properties.PropertySheetEntry.setValues(PropertySheetEntry.java:736)
> at org.eclipse.ui.views.properties.PropertySheetViewer.setInput(PropertySheetViewer.java:986)
> at org.eclipse.ui.views.properties.PropertySheetPage.selectionChanged(PropertySheetPage.java:518)
> at org.jboss.tools.openshift.internal.ui.property.tabbed.OpenShiftResourcePropertySection$2.selectionChanged(OpenShiftResourcePropertySection.java:135)
> at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163)
> 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.Viewer.fireSelectionChanged(Viewer.java:160)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197)
> at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257)
> at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242)
> at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408)
> 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)
10 years