June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Roland Grunberg commented on JBDS-3739: --------------------------------------- This has been fixed recently at https://bugs.eclipse.org/bugs/show_bug.cgi?id=495293 . As it was an important bug fix, it made our RC4 candidate. The problem seems to happen due to an image that has an empty list of repository tags as opposed to the standard ["<none>:<none>"] in cases where none exist. > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Priority: Blocker > Labels: havoc > Attachments: docker-frozen.txt > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9442) Investigate possibility for remote debug launch of app servers

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9442?page=com.atlassian.jira.plugin... ] Rob Stryker resolved JBIDE-9442. -------------------------------- Resolution: Done Seems this was fixed as part of following commit: {code} commit 6eb6d04b54357862f4ed5bbef938a655f29d5b28 Author: Rob Stryker <rob(a)oxbeef.net> Date: Mon May 23 13:39:49 2016 -0400 JBIDE-21059 - expand adding debugger to local servers run externally Refactor some internal classes Ensure attach-debugger setting is respected {code} So this should be working 100% as expected in 4.4.0.Final. > Investigate possibility for remote debug launch of app servers > -------------------------------------------------------------- > > Key: JBIDE-9442 > URL: https://issues.jboss.org/browse/JBIDE-9442 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.4.0.Final, 4.4.0.Alpha2 > > > When launching a remote server on a remote host, we do not currently connect a remote debugger. It'd be nice if we also connected a remote debugger if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9442) Investigate possibility for remote debug launch of app servers

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9442?page=com.atlassian.jira.plugin... ] Rob Stryker updated JBIDE-9442: ------------------------------- Fix Version/s: 4.4.0.Final > Investigate possibility for remote debug launch of app servers > -------------------------------------------------------------- > > Key: JBIDE-9442 > URL: https://issues.jboss.org/browse/JBIDE-9442 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha2, 4.4.0.Final > > > When launching a remote server on a remote host, we do not currently connect a remote debugger. It'd be nice if we also connected a remote debugger if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Marián Labuda commented on JBDS-3739: ------------------------------------- For me docker connection is not working neither. At first I thought it's happening only after restart, but also on new connection (just created) by first run of CDK in devstudio, I cannot work with docker connection. I am running nightly CDK 2.1 with box rhel-7-cdk-vagrant-scratch-7.2.02062016-1.x86_64.vagrant-virtualbox.box and in devstudio Verified in devstudio with build id: GA-v20160603-0516-B5506. Getting following error: {code} An internal error occurred during: "Opening connection to https://10.1.2.2:2376 ". java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:653) at java.util.ArrayList.get(ArrayList.java:429) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:940) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:867) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.setState(DockerConnection.java:307) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.ping(DockerConnection.java:322) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:265) at org.eclipse.linuxtools.internal.docker.ui.commands.EnableConnectionCommandHandler$1.run(EnableConnectionCommandHandler.java:53) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Priority: Blocker > Labels: havoc > Attachments: docker-frozen.txt > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Roland Grunberg commented on JBDS-3739: --------------------------------------- [~mmalina], does the icon for the connection in the Docker Explorer appear to be grey when you're attempting to browse ? There should be a button beside add/remove connections, that will re-enable the connection if it has been disabled. If you try clicking it does it restore the connection ? > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Priority: Blocker > Labels: havoc > Attachments: docker-frozen.txt > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22505) Deploy Docker Image wizard: ImageSearch changed in API, wont compile any more

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22505?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22505. --------------------------------- Jenkins jobs are back to normal. Closing. > Deploy Docker Image wizard: ImageSearch changed in API, wont compile any more > ----------------------------------------------------------------------------- > > Key: JBIDE-22505 > URL: https://issues.jboss.org/browse/JBIDE-22505 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Xavier Coulon > Priority: Blocker > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.0.Final > > > ImageSearch broke API at some point. Current 2.0.0.201606010301 that we use in OpenShift wont allow > {code} > new ImageSearch(IDockerConnection conn, String name) > {code} > The new API now is: > {code} > new ImageSearch(IDockerConnection conn, String name, IRegistry reg) > {code} > reg cant be set to *null*, even though it now compiles and you can open up the search dialog. But searches wont find anything, the results stay empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22510) Unable to display tags for jboss/wildfly Docker image

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22510?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22510. --------------------------------- Tags are correct, test is skipped. Verified in: Version: 10.0.0.GA Build id: GA-v20160603-0010-B5505 Build date: 20160603-0010 > Unable to display tags for jboss/wildfly Docker image > ----------------------------------------------------- > > Key: JBIDE-22510 > URL: https://issues.jboss.org/browse/JBIDE-22510 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Final > > > This is reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=495338 > In the mean time, we should disable the {{DockerHubRegistryTest}} tests to avoid the build failures on Jenkins. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22380) New Application wizard: project is not preselected (nor can you select any) if launched from explorer

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22380?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22380. --------------------------------- Closing as cannot reproduce. > New Application wizard: project is not preselected (nor can you select any) if launched from explorer > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-22380 > URL: https://issues.jboss.org/browse/JBIDE-22380 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Final > > Attachments: project-not-preselected.png > > Original Estimate: 8 minutes > Remaining Estimate: 8 minutes > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Martin Malina reassigned JBDS-3739: ----------------------------------- Resolution: (was: Done) Assignee: Xavier Coulon (was: Marián Labuda) Fix Version/s: (was: 10.0.0.GA) I tried this again today with cdk 2.1 nightly and now it doesn't work. When I first start CDK in JBoss Tools 4.4 (latest nightly + latest docker tooling), docker connection is created and works - I can browse images. But when I stop cdk and start again, the docker connection will no longer work. When I stop cdk, remove the connection and start again, it will work. > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Priority: Blocker > Labels: havoc > Attachments: docker-frozen.txt > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-654: ---------------------------------- The runtime can be whatever makes most sense - I'm currently picking up http://origin-repository.jboss.org/nexus/content/groups/ea/org/jboss/fuse... for testing purposes. The installer will work on all supported OS'. I bounced the extraction of the runtime from the installer jar off of Denis G. Since it really isn't a p2-director task to extract an embedded zip - his suggestion was to create a new izpack installer build based on devstudio one as opposed to trying to extend the devstudio installer. I'm looking into that now. > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: Capture.JPG, inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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