June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-237) NPE after enabling disabled connection [EBZ#495198]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-237?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-237: ------------------------------ Sprint: devex #115 May 2016 > NPE after enabling disabled connection [EBZ#495198] > --------------------------------------------------- > > Key: ERT-237 > URL: https://issues.jboss.org/browse/ERT-237 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > Enabling a connection that is disabled will cause an NPE to occur in DockerConnection listContainers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3918) Latest DevStudio build starts without splash screen

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3918?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3918: ----------------------------- > Latest DevStudio build starts without splash screen > --------------------------------------------------- > > Key: JBDS-3918 > URL: https://issues.jboss.org/browse/JBDS-3918 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: p2-product > Affects Versions: 10.0.0.GA > Environment: OS: > Windows 10 > Devstudio: > Version: 10.0.0.Alpha3 > Build id: Alpha3-v20160601-0425-B5485 > Build date: 20160601-0425 > Reporter: Denis Golovin > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.GA > > > Latest nightly build downloaded bu Development Suite installer starts without splash screen -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3918) Latest DevStudio build starts without splash screen

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3918?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3918: -------------------------------- > Latest DevStudio build starts without splash screen > --------------------------------------------------- > > Key: JBDS-3918 > URL: https://issues.jboss.org/browse/JBDS-3918 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: p2-product > Affects Versions: 10.0.0.GA > Environment: OS: > Windows 10 > Devstudio: > Version: 10.0.0.Alpha3 > Build id: Alpha3-v20160601-0425-B5485 > Build date: 20160601-0425 > Reporter: Denis Golovin > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.GA > > > Latest nightly build downloaded bu Development Suite installer starts without splash screen -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3918) Latest DevStudio build starts without splash screen

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3918?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3918: ----------------------------- Status: New (was: New) Target Release: 10.0.0.GA > Latest DevStudio build starts without splash screen > --------------------------------------------------- > > Key: JBDS-3918 > URL: https://issues.jboss.org/browse/JBDS-3918 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: p2-product > Affects Versions: 10.0.0.GA > Environment: OS: > Windows 10 > Devstudio: > Version: 10.0.0.Alpha3 > Build id: Alpha3-v20160601-0425-B5485 > Build date: 20160601-0425 > Reporter: Denis Golovin > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.GA > > > Latest nightly build downloaded bu Development Suite installer starts without splash screen -- 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 Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3739: -------------------------------------- [~mmalina] so it looks like we can close this issue? And follow up in JBIDE-22501 > 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: Marián Labuda > Priority: Blocker > Labels: havoc > Fix For: 10.0.0.GA > > 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 Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-3739. ---------------------------------- Resolution: Done > 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: Marián Labuda > Priority: Blocker > Labels: havoc > Fix For: 10.0.0.GA > > 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-22501) CDK stuck on Starting... after launch

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22501?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22501: ---------------------------------------- Did you see it before? Using devstudio 9.1.0. It's not 100% reproducible, correct? > CDK stuck on Starting... after launch > ------------------------------------- > > Key: JBIDE-22501 > URL: https://issues.jboss.org/browse/JBIDE-22501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.x > > > This happened to me a few times and I think I mentioned it in a JIRA, but AFAIK there is no separate JIRA for this. > This is what I did today (verifying JBDS-3739): > 1. Start my Eclipse Neon RC2 > 2. Updated Eclipse > 3. Updated Docker Tools to latest nightly > 4. Installed nightly JBoss Tools Abridged > 5. Set up cdk server (CDK 2.0 on my disk, already set up and started several times before) > 6. Start CDK server > Everything fine here - after some time it's Started, I accepted the OpenShift cert, Docker connection worked. > 7. Stop CDK server > 8. Start CDK server > This time it's stuck on Starting... even though I can see from the console that the vagrant box started: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Clearing any previously set forwarded ports... > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Remote connection disconnect. Retrying... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Configuring and enabling network interfaces... > ==> default: Registering box with vagrant-registration... > ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Rsyncing folder: /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/ => /vagrant > ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision` > ==> default: flag to force provisioning. Provisioners marked to run always will still run. > {code} > Now it will probably time out and stop the server. And most probably next start will work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22501) CDK stuck on Starting... after launch

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22501?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22501: ----------------------------------- Priority: Critical (was: Major) > CDK stuck on Starting... after launch > ------------------------------------- > > Key: JBIDE-22501 > URL: https://issues.jboss.org/browse/JBIDE-22501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.x > > > This happened to me a few times and I think I mentioned it in a JIRA, but AFAIK there is no separate JIRA for this. > This is what I did today (verifying JBDS-3739): > 1. Start my Eclipse Neon RC2 > 2. Updated Eclipse > 3. Updated Docker Tools to latest nightly > 4. Installed nightly JBoss Tools Abridged > 5. Set up cdk server (CDK 2.0 on my disk, already set up and started several times before) > 6. Start CDK server > Everything fine here - after some time it's Started, I accepted the OpenShift cert, Docker connection worked. > 7. Stop CDK server > 8. Start CDK server > This time it's stuck on Starting... even though I can see from the console that the vagrant box started: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Clearing any previously set forwarded ports... > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Remote connection disconnect. Retrying... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Configuring and enabling network interfaces... > ==> default: Registering box with vagrant-registration... > ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Rsyncing folder: /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/ => /vagrant > ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision` > ==> default: flag to force provisioning. Provisioners marked to run always will still run. > {code} > Now it will probably time out and stop the server. And most probably next start will work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22501) CDK stuck on Starting... after launch

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22501?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22501: ----------------------------------- Fix Version/s: 4.4.x > CDK stuck on Starting... after launch > ------------------------------------- > > Key: JBIDE-22501 > URL: https://issues.jboss.org/browse/JBIDE-22501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.x > > > This happened to me a few times and I think I mentioned it in a JIRA, but AFAIK there is no separate JIRA for this. > This is what I did today (verifying JBDS-3739): > 1. Start my Eclipse Neon RC2 > 2. Updated Eclipse > 3. Updated Docker Tools to latest nightly > 4. Installed nightly JBoss Tools Abridged > 5. Set up cdk server (CDK 2.0 on my disk, already set up and started several times before) > 6. Start CDK server > Everything fine here - after some time it's Started, I accepted the OpenShift cert, Docker connection worked. > 7. Stop CDK server > 8. Start CDK server > This time it's stuck on Starting... even though I can see from the console that the vagrant box started: > {code} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Clearing any previously set forwarded ports... > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Remote connection disconnect. Retrying... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! Guest > default: additions are required for forwarded ports, shared folders, host only > default: networking, and more. If SSH fails on this machine, please install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work properly, > default: in which case you may ignore this message. > ==> default: Configuring and enabling network interfaces... > ==> default: Registering box with vagrant-registration... > ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > ==> default: Rsyncing folder: /Users/rasp/jbossqa/cdk/cdk/components/rhel/rhel-ose/ => /vagrant > ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision` > ==> default: flag to force provisioning. Provisioners marked to run always will still run. > {code} > Now it will probably time out and stop the server. And most probably next start will work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21850) Maven project has wrong context root set up after import

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21850?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-21850: ----------------------------------- Fix Version/s: 4.4.0.Final > Maven project has wrong context root set up after import > -------------------------------------------------------- > > Key: JBIDE-21850 > URL: https://issues.jboss.org/browse/JBIDE-21850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, maven > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Fix For: 4.4.0.Final > > > Importing maven project (in my case "servlet-security" from EAP quickstarts) via easymport has wrong context root (right click on project->Properties->Web Project Settings) configured. > Name of project is servlet-security, but web context root is jboss-servlet-security > This results into 404 when this project gets deployed to server. IDE opens url http://localhost:8080/jboss-servlet-security, but correct url is http://localhost:8080/servlet-security. > Note, that this does not happen when importing this project as existing maven project (not using easymport). -- 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