December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20726) Docker explorer - Default setting should be to display and not hide stopped containers

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20726?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-20726. ----------------------------------- Resolution: Done Labels: new_and_noteworthy (was: ) Resolved in https://git.eclipse.org/r/62379 > Docker explorer - Default setting should be to display and not hide stopped containers > -------------------------------------------------------------------------------------- > > Key: JBIDE-20726 > URL: https://issues.jboss.org/browse/JBIDE-20726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta2 > > > By default, only running containers are shown in the Docker explorer view - I think that users will expect to see all containers by default. The OOTB default setting should be changed to show all containers. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19978) Docker Images and Containers view do not display count at the top of the view

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19978?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-19978: --------------------------------------- [~mmalina], do you still have this issue ? > Docker Images and Containers view do not display count at the top of the view > ----------------------------------------------------------------------------- > > Key: JBIDE-19978 > URL: https://issues.jboss.org/browse/JBIDE-19978 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.3.x > > Attachments: docker-no-count.png, images-count-missing.png > > > After establishing a connection to my Docker instance, the Docker Images view shows active images. At the top, it should display something like (4/31 Images), but at first it doesn't show this. > If I selected Show all images, and then uncheck it again, the numbers are now shown. > In a previous attempt, during the download of the wildfly image, the numbers were shown, but once the pulling finished, the numbers disappeared. > Similarly, in the Docker Containers view, when you first create a docker connection, the numbers are not there. But once I check Show all containers and uncheck it again, it will properly show (0/1 Containers). > Upstream BZ is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=469628 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19974) Cannot detect running boot2docker on OS X

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19974?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19974: ---------------------------------- Fix Version/s: 4.3.1.Beta1 (was: 4.3.x) > Cannot detect running boot2docker on OS X > ----------------------------------------- > > Key: JBIDE-19974 > URL: https://issues.jboss.org/browse/JBIDE-19974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.3.1.Beta1 > > > In Docker Explorer, when I want to create my first connection, I click on the link to create a connection, the dialog is opened and I get this in my Error View: > bash: no job control in this shell > An exception stack trace is not available. > Another warning is generated also: > Could not find default settings to connect to a local Docker daemon > An exception stack trace is not available. > I'm on OS X and have boot2docker running. By default, boot2docker will not add the DOCKER variables to .bash_profile, it will only instruct me to set them up like this: > export DOCKER_HOST=tcp://192.168.59.103:2376 > export DOCKER_CERT_PATH=/Users/rasp/.boot2docker/certs/boot2docker-vm > export DOCKER_TLS_VERIFY=1 > With the way the script in the Docker Tooling works (env | grep DOCKER), it cannot detect the variables unless they are in .bash_profile. > But even if I added them there (and a new Terminal window has these variables), Eclipse still can't detect the running Docker instance. > So something is wrong. > I logged an upstream bug here: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=469624 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20732) Support for build options

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20732?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-20732: ---------------------------------- Fix Version/s: 4.3.1.Beta1 (was: 4.3.x) > Support for build options > ------------------------- > > Key: JBIDE-20732 > URL: https://issues.jboss.org/browse/JBIDE-20732 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1 > > > see https://bugs.eclipse.org/bugs/show_bug.cgi?id=474196 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20732) Support for build options

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20732?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-20732. ----------------------------------- Resolution: Done Labels: new_and_noteworthy (was: ) > Support for build options > ------------------------- > > Key: JBIDE-20732 > URL: https://issues.jboss.org/browse/JBIDE-20732 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1 > > > see https://bugs.eclipse.org/bugs/show_bug.cgi?id=474196 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21294) NPE when starting CDK server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21294?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21294: -------------------------------- Fix Version/s: 4.3.0.Beta1 > NPE when starting CDK server > ---------------------------- > > Key: JBIDE-21294 > URL: https://issues.jboss.org/browse/JBIDE-21294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > I've been testing the CDK adapter with [1] today and when I tried to start again from scratch (vagrant destroy + new workspace) and added the server again and started, I got a NPE: > {code} > An internal error occurred during: "Starting cdk-v2 CDK Server". > java.lang.NullPointerException > at java.io.File.<init>(File.java:277) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:133) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > I did add the user credentials in the server editor. > Now I looked in the launch config and the first field at the top is empty - it should contain path to vagrant. I'm not sure why it's missing - I just used runtime detection. But in any case, the NPE should be handled somehow. > [1] https://github.com/redhat-developer-tooling/openshift-vagrant -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20422) Docker explorer - Stopping a container removes it from the explorer display

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20422?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-20422: ---------------------------------- Fix Version/s: 4.3.1.Beta1 (was: 4.3.x) > Docker explorer - Stopping a container removes it from the explorer display > --------------------------------------------------------------------------- > > Key: JBIDE-20422 > URL: https://issues.jboss.org/browse/JBIDE-20422 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker, upstream > Affects Versions: 4.3.0.Beta2 > Environment: RHEL 7 > Java 8 > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Fix For: 4.3.1.Beta1 > > > Once the container is removed from the Docker explorer, the user must go to the CLI to restart it and have it appear again in the explorer. > Why not leave it visible in the Docker explorer and mark it as stopped? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20422) Docker explorer - Stopping a container removes it from the explorer display

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20422?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-20422. ----------------------------------- Resolution: Done > Docker explorer - Stopping a container removes it from the explorer display > --------------------------------------------------------------------------- > > Key: JBIDE-20422 > URL: https://issues.jboss.org/browse/JBIDE-20422 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker, upstream > Affects Versions: 4.3.0.Beta2 > Environment: RHEL 7 > Java 8 > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Fix For: 4.3.1.Beta1 > > > Once the container is removed from the Docker explorer, the user must go to the CLI to restart it and have it appear again in the explorer. > Why not leave it visible in the Docker explorer and mark it as stopped? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20734) Show ports, environment variables and links in the UI

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20734?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-20734: ---------------------------------- Fix Version/s: 4.3.1.Beta1 (was: 4.3.x) > Show ports, environment variables and links in the UI > ----------------------------------------------------- > > Key: JBIDE-20734 > URL: https://issues.jboss.org/browse/JBIDE-20734 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1 > > > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=471666 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20734) Show ports, environment variables and links in the UI

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20734?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-20734. ----------------------------------- Resolution: Done Labels: new_and_noteworthy (was: ) > Show ports, environment variables and links in the UI > ----------------------------------------------------- > > Key: JBIDE-20734 > URL: https://issues.jboss.org/browse/JBIDE-20734 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1 > > > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=471666 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 December 2015