[JBoss JIRA] (JBIDE-21949) Allow user to turn on/off showing console when output changes
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21949:
-------------------------------------
Summary: Allow user to turn on/off showing console when output changes
Key: JBIDE-21949
URL: https://issues.jboss.org/browse/JBIDE-21949
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
At the moment every publish to OpenShift via rsync show console with output from rsync (done in JBIDE-21326). User is forced to see console output. It would be nice if I could disable/enable showing console output when content changes. Something like server's console output has - toggle button Show Console Output When Standard Out Changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21326) Server Adapter: Publishing is not telling me what it's doing
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21326?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21326.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin build B246.
> Server Adapter: Publishing is not telling me what it's doing
> ------------------------------------------------------------
>
> Key: JBIDE-21326
> URL: https://issues.jboss.org/browse/JBIDE-21326
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Xavier Coulon
> Priority: Critical
> Labels: new_and_noteworthy, openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
>
> Currently we dont tell the user what we're syncing up to the pod. We should open up a console that shows the (std) output of the "oc rsync" cmd that we're running behind the scenes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3607) Update Suite installer UI/names
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/JBDS-3607?page=com.atlassian.jira.plugin.... ]
Pavol Pitonak updated JBDS-3607:
--------------------------------
Attachment: installer_version.png
[~joqian], we're displaying installer's version on first page (see the attached screenshot). Should we hide it or will you update your flows so that we can implement it as designed? The primary reason for having it displayed is that in the case of a bug, user can tell us which version they are running (this info should be also in installation log).
> Update Suite installer UI/names
> -------------------------------
>
> Key: JBDS-3607
> URL: https://issues.jboss.org/browse/JBDS-3607
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: installer
> Reporter: Max Rydahl Andersen
> Assignee: Joshua Wilson
> Priority: Blocker
> Labels: havoc, ui
> Fix For: 9.1.0.CR1
>
> Attachments: Installer flow.pdf, installer_version.png
>
>
> Suite Installer should use Red Hat Developer style. more details to follow.
> https://patternfly.atlassian.net/browse/RHUAP-26
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21857:
---------------------------------------------
Okey, I now grok this issue better and I think it is either expected behavior or due to us handling the restart our self now.
The issue boils down to (variation of [~fbricon] comment):
1) jvm started and debugger connected (all is good)
2) user make a method body change - debugger tells jvm - all is good. no restarts needed.
3) user make a structural change - debugger tells jvm - jvm does not support it. user is warned. (debugger and jvm is out of sync)
4) restart just the deployment - change is now visible (debugger and jvm is still out of sync)
5) do a method body chance - debugger tells jvm - debugger still out of sync, user asked to restart.
#5 *could* just be our custom code for handling the restart on failed change that is not handling this case properly.
In the past (1+ year ago) we didn't do that.
Before we raise this to be a JDK limitation is there a way we can disable that custom logic and see if eclipse plain hotswap failure logic works ? [~rob.stryker] ?
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-540) unknown Central categories referenced by JBTIS connectors
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-540?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-540.
-----------------------------------
Verified with JBT 4.3.1.Beta2 + JBTIS 4.3.0.Beta1
> unknown Central categories referenced by JBTIS connectors
> ---------------------------------------------------------
>
> Key: JBTIS-540
> URL: https://issues.jboss.org/browse/JBTIS-540
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 4.3.0.Alpha2, 9.0.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Paul Leacu
> Fix For: 4.3.0.Beta1
>
>
> After installing all of JBT 4.3.1.Beta1 from http://download.jboss.org/jbosstools/mars/staging/updates/ into eclipse-jee-mars-1-RC3-linux-gtk-x86_64.tar.gz, then installing all the stuff in Central (including EA content) EXCEPT JRebel and Android connectors, I see this in my console:
> {code}
> !MESSAGE Unknown category 'org.jboss.tools.discovery.certification.supported' referenced by connector 'org.jboss.runtime.drools.detector.feature' declared in
> org.jboss.tools.central.discovery.integration_stack_4.3.0.Alpha2_v20151006_1928_B438.jar_7462569064950840915.jar
> !MESSAGE Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.bpel.feature' declared in
> org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2_v20151006_1928_B438.jar_6615978320114197060.jar
> !MESSAGE Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.drools.eclipse.feature' declared in
> org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2_v20151006_1928_B438.jar_6615978320114197060.jar
> !MESSAGE Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.guvnor.tools.feature' declared in
> org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2_v20151006_1928_B438.jar_6615978320114197060.jar
> {code}
--
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:59 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.
!!!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, 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] (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:59 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.
!!!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, 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] (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 updated JBIDE-21916:
---------------------------------
Attachment: 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, 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