June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22617) Integrate DockViz in to Docker Tooling

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22617?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-22617: ---------------------------------- Summary: Integrate DockViz in to Docker Tooling (was: Integrate DockViz in to JBoss docker Tools) > Integrate DockViz in to Docker Tooling > -------------------------------------- > > Key: JBIDE-22617 > URL: https://issues.jboss.org/browse/JBIDE-22617 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.4.0.Alpha2 > Reporter: Mustafa Musaji > Assignee: Xavier Coulon > Priority: Optional > > DockVIz is a tool used to provide a way to view docker information on a system in a number of ways, one of which is a tree like structure to be able to visualise docker layers. > This would be a nice thing to include in our docker toolset. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22617) Integrate DockViz in to Docker Tooling

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22617?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-22617: --------------------------------------- I opened this issue upstream after we started discussing about it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=496308 > Integrate DockViz in to Docker Tooling > -------------------------------------- > > Key: JBIDE-22617 > URL: https://issues.jboss.org/browse/JBIDE-22617 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.4.0.Alpha2 > Reporter: Mustafa Musaji > Assignee: Xavier Coulon > Priority: Optional > > DockVIz is a tool used to provide a way to view docker information on a system in a number of ways, one of which is a tree like structure to be able to visualise docker layers. > This would be a nice thing to include in our docker toolset. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22597) Deploy Docker wizard: Deploy docker image to openshift may finish without user being notified

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22597?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22597: ------------------------------------- Labels: deploy_docker_wizard openshift_v3 (was: ) > Deploy Docker wizard: Deploy docker image to openshift may finish without user being notified > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22597 > URL: https://issues.jboss.org/browse/JBIDE-22597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.S116 > > > When a Docker image is deployed to Openshift and this is an update (Openshift resources already exist), then image is pushed to the registry but no feedback is returned to the user. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22597) Deploy Docker wizard: Deploy docker image to openshift may finish without user being notified

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22597?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22597: ------------------------------------- Summary: Deploy Docker wizard: Deploy docker image to openshift may finish without user being notified (was: Deploy docker image to openshift may finish without user being notified) > Deploy Docker wizard: Deploy docker image to openshift may finish without user being notified > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22597 > URL: https://issues.jboss.org/browse/JBIDE-22597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Fix For: 4.4.1.S116 > > > When a Docker image is deployed to Openshift and this is an update (Openshift resources already exist), then image is pushed to the registry but no feedback is returned to the user. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-311) Create Container progress dialog stuck on 100% [EBZ#496380]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-311: --------------------------------------- Summary: Create Container progress dialog stuck on 100% [EBZ#496380] Key: ERT-311 URL: https://issues.jboss.org/browse/ERT-311 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Created attachment 262534 DB client settings When I was trying to adapt guide on https://hub.docker.com/_/mariadb/ for mariadb the Progress bar is showing Create Container: (100%), but the container is running. Steps to reproduce: 1. Create mariadb: Adapt command ("docker run --name some-mariadb -e MYSQL_ROOT_PASSWORD=password -d mariadb:tag") for "Run a Docker Image" wizard and run. The database should be running without issues. 2. Connect to database with MySQL client: Adapt command ("docker run -it --link some-mariadb:mysql --rm mariadb sh -c 'exec mysql -h*tcp address of running database* -P3306 -uroot -ppassword'") for Docker Tooling in Docker Container settings and run. The client is running and you can work with it, but progress bar still showing message: "Create Container: (100%)". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-145) Grunt is not available in the Quick access [EBZ#492125]

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/ERT-145?page=com.atlassian.jira.plugin.sy... ] Shane Bryzak resolved ERT-145. ------------------------------ Assignee: Shane Bryzak Resolution: Done > Grunt is not available in the Quick access [EBZ#492125] > ------------------------------------------------------- > > Key: ERT-145 > URL: https://issues.jboss.org/browse/ERT-145 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Shane Bryzak > Labels: General, bzira > > "Run as Grunt task" is not available via quick access. Basically, selection should be tracked and the following behavior is expected: > - IProject with gruntfile.js (launch default task from gruntfile.js) > - IFile gruntfile.js (default task should be run) > - ITask (run grunt task) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22362: ------------------------------------------ [~ibuziuk] [~mlabuda] I really think that we should have DEV_MODE enabled by default at least in our server adapter (create the app via template which has DEV_MODE disabled, then create the server adapter wich turns DEV_MODE=true by default). IMHO it's completely unexpected for the user to get an application that he cannot modify while the others (eap, php, etc.) are all modifyable by default. The other question I am wondering about is that the casual nodejs users which are using the cmd-line (oc) will have the very same experience: They'll just wondering about no changes being propagated - when doing oc rsync - unless they read the documentation and discover that they first have to enable DEV_MODE. Doesnt seem ideal to me. > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.S116 > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22362 at 6/20/16 6:20 AM: ------------------------------------------------------------------- [~ibuziuk] [~mlabuda] I really think that we should have DEV_MODE enabled by default at least in our server adapter (create the app via template which has DEV_MODE disabled, then create the server adapter wich turns DEV_MODE=true by default). IMHO it's completely unexpected for the user to get an application that he cannot modify while the others (eap, php, etc.) are all modifyable by default. The other question I am wondering about is that the casual nodejs users which are using the cmd-line (oc) will have the very same experience: They'll just wondering about no changes being propagated - when doing oc rsync - unless they read the documentation and discover that they first have to enable DEV_MODE. Doesnt seem ideal to me. CC: [~fbricon] was (Author: adietish): [~ibuziuk] [~mlabuda] I really think that we should have DEV_MODE enabled by default at least in our server adapter (create the app via template which has DEV_MODE disabled, then create the server adapter wich turns DEV_MODE=true by default). IMHO it's completely unexpected for the user to get an application that he cannot modify while the others (eap, php, etc.) are all modifyable by default. The other question I am wondering about is that the casual nodejs users which are using the cmd-line (oc) will have the very same experience: They'll just wondering about no changes being propagated - when doing oc rsync - unless they read the documentation and discover that they first have to enable DEV_MODE. Doesnt seem ideal to me. > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.S116 > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-144) Gulp is not available in the Quick access [EBZ#492124]

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/ERT-144?page=com.atlassian.jira.plugin.sy... ] Shane Bryzak resolved ERT-144. ------------------------------ Resolution: Done > Gulp is not available in the Quick access [EBZ#492124] > ------------------------------------------------------ > > Key: ERT-144 > URL: https://issues.jboss.org/browse/ERT-144 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Shane Bryzak > Labels: General, bzira > > "Run as Gulp task" is not available via quick access. Basically, selection should be tracked and the following behavior is expected: > - IProject with gulpfile.js (launch default task from gulpfile.js) > - IFile gulpfile.js (default task should be run) > - ITask (run gulp task) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-310) Chars are not correctly parsed when building an image in Docker Console [EBZ#496377]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-310: --------------------------------------- Summary: Chars are not correctly parsed when building an image in Docker Console [EBZ#496377] Key: ERT-310 URL: https://issues.jboss.org/browse/ERT-310 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Priority: Minor Created attachment 262532 Build Docker Image Output When I am building an image, not all chars are correctly parsed: the console output is not very well readable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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