June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19947) OpenShift v3 plugin can't work after update

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19947?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19947: ------------------------------------------ [~deshuai] I had a fresh Ecipse install which was using my default jdk which is a jdk 1.7. I could install without problems. When then running my EClipse with openshift installed I faced the above warning that [~nickboldt] pasted. The warning clearly states that you need to use jdk 1.8. So if you're not you cant expect things to work, you need to change your Eclipse to use jdk1.8 [~deshuai] how was it when updating? Didnt you get the above warning when running Eclipse? > OpenShift v3 plugin can't work after update > ------------------------------------------- > > Key: JBIDE-19947 > URL: https://issues.jboss.org/browse/JBIDE-19947 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Ma Deshuai > Attachments: error1.jpg, error2.jpg, error3.jpg, JDK7-warning.png > > > Description of problem: > After update openshift v3 plugin from uri:http://download.jboss.org/jbosstools/updates/nightly/mars/. Can't open openshift v3 plug in eclipse. > Version-Release number of selected component (if applicable): > Eclipse: mars > Jdk: 1.7 > OpenShift plug : 3.0.0.Beta1-v20150604-1037-B825 > How reproducible: > Always > Steps to Reproduce: > 1.Update OpenShift v3 plugin from http://download.jboss.org/jbosstools/updates/nightly/mars/ > 2.Restart eclipse and open "OpenShift Explorer" > Actual results: > 2.Open "OpenShift Explorer" with error > Could not create the view: org.jboss.tools.openshift.express.ui.explorer.expressConsoleView > Expected results: > 2.Open "OpenShift Explorer" corectly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19986) Updatesite contains Beta2 version plugins

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-19986: ---------------------------------- Summary: Updatesite contains Beta2 version plugins Key: JBIDE-19986 URL: https://issues.jboss.org/browse/JBIDE-19986 Project: Tools (JBoss Tools) Issue Type: Bug Components: updatesite Affects Versions: 4.3.0.Beta1 Reporter: Radim Hopp Namely: o.j.t.common.* o.j.t.foundation.* o.j.t.runtime o.j.t.stacks o.j.t.usage -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19560) Display Container info/inspect in properties view

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19560?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19560. --------------------------------- Verified in JBDS 9.0.0.Beta1 B34 > Display Container info/inspect in properties view > ------------------------------------------------- > > Key: JBIDE-19560 > URL: https://issues.jboss.org/browse/JBIDE-19560 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Beta1 > > > Show the equivalent of 'docker ps' and 'docker inspect' in the tabs of a properties view when a Docker container node is selected in the Docker Explorer view. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19971) OSE v2 prompts user to enter kerberos credentials from command line while importing an application

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19971?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-19971: --------------------------------------- Well I did more diggins. [~rhopp] tried same scenario and he was not experiencing this issue. I tested it several times with different conditions: * usually I am using kerberos ticket (kinit), so skipped it this time * I have specific config for SSH keys in .ssh folder so I temporarily disabled ssh config result is still the same. The prompt on screencasts above is still shown and without entering valid credentials application is not cloned to local repo. > OSE v2 prompts user to enter kerberos credentials from command line while importing an application > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19971 > URL: https://issues.jboss.org/browse/JBIDE-19971 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Priority: Blocker > Attachments: authorized.png, creds_prompt.png, jstack.txt > > > Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) there is hanged importing job in IDE. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there. > Prompt from CLI looks like: > Kerberos username [mlabuda]: > Kerberos password for mlabuda: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19971) OSE v2 prompts user to enter kerberos credentials from command line while importing an application

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19971?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-19971 at 6/9/15 4:20 AM: --------------------------------------------------------------- Well I did more digging around it. [~rhopp] tried same scenario and he was not experiencing this issue. I tested it several times with different conditions: * usually I am using kerberos ticket (kinit), so skipped it this time * I have specific config for SSH keys in .ssh folder so I temporarily disabled ssh config result is still the same. The prompt on screencasts above is still shown and without entering valid credentials application is not cloned to local repo. was (Author: mlabuda): Well I did more diggins. [~rhopp] tried same scenario and he was not experiencing this issue. I tested it several times with different conditions: * usually I am using kerberos ticket (kinit), so skipped it this time * I have specific config for SSH keys in .ssh folder so I temporarily disabled ssh config result is still the same. The prompt on screencasts above is still shown and without entering valid credentials application is not cloned to local repo. > OSE v2 prompts user to enter kerberos credentials from command line while importing an application > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19971 > URL: https://issues.jboss.org/browse/JBIDE-19971 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Priority: Blocker > Attachments: authorized.png, creds_prompt.png, jstack.txt > > > Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) there is hanged importing job in IDE. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there. > Prompt from CLI looks like: > Kerberos username [mlabuda]: > Kerberos password for mlabuda: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19971) OSE v2 prompts user to enter kerberos credentials from command line while importing an application

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19971?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-19971 at 6/9/15 4:20 AM: --------------------------------------------------------------- Well I did more digging around it. [~rhopp] tried same scenario and he was not experiencing this issue. I tested it several times with different conditions: * usually I am using kerberos ticket (kinit), so skipped it this time * I have specific config for SSH keys in .ssh folder so I temporarily disabled ssh config result is still the same. The prompt on screencasts above is still shown and without entering valid credentials application is not cloned to local repo. was (Author: mlabuda): Well I did more digging around it. [~rhopp] tried same scenario and he was not experiencing this issue. I tested it several times with different conditions: * usually I am using kerberos ticket (kinit), so skipped it this time * I have specific config for SSH keys in .ssh folder so I temporarily disabled ssh config result is still the same. The prompt on screencasts above is still shown and without entering valid credentials application is not cloned to local repo. > OSE v2 prompts user to enter kerberos credentials from command line while importing an application > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19971 > URL: https://issues.jboss.org/browse/JBIDE-19971 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Priority: Blocker > Attachments: authorized.png, creds_prompt.png, jstack.txt > > > Right on the importing a new OpenShift application from OpenShift Enterprise v2 server (used internal ITOS instance) there is hanged importing job in IDE. After exploration I found out that it's caused because there is a prompt to enter credentials from terminal (the same one where I run IDE by running ./jbdevstudio. It is really annoying bcs such prompt is on every import of any application. Even the kerberos ticket has been established, the prompt is there. > Prompt from CLI looks like: > Kerberos username [mlabuda]: > Kerberos password for mlabuda: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13414) No Error reported when WS Client code generation fails

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-13414. ------------------------------- Verified, closing. > No Error reported when WS Client code generation fails > ------------------------------------------------------ > > Key: JBIDE-13414 > URL: https://issues.jboss.org/browse/JBIDE-13414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Mustafa Musaji > Assignee: Brian Fitzpatrick > Labels: jax-ws, web_service_client > Fix For: 4.3.0.Beta1 > > Attachments: echoService.wsdl, new-error.png, screenshot-1.png > > > If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: > Failed to invoke WSDLToJava > org.apache.cxf.tools.common.ToolException: Thrown by JAXB: > Thrown by JAXB: > Two declarations cause a collision in the ObjectFactory class. > ... > However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19563) Save docker connections in plugin preferences

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19563?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19563. --------------------------------- Verified in JBDS 9.0.0.Beta1 B34 > Save docker connections in plugin preferences > --------------------------------------------- > > Key: JBIDE-19563 > URL: https://issues.jboss.org/browse/JBIDE-19563 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Beta1 > > > In the current code, the Docker connections are not saved when exiting the workspace, so they need to be setup again after restart -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3411) have installer build actually use M6 p2 product build

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3411?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3411. ----------------------------- Verified, closing. > have installer build actually use M6 p2 product build > ----------------------------------------------------- > > Key: JBDS-3411 > URL: https://issues.jboss.org/browse/JBDS-3411 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer, updatesite > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > talking with [~prapicault] I learned that since M6 the following changes are required for proper working p2 product/osx build: > {code} > <products> > <product> > ... > <rootFolders> > <macosx>MyProduct.app</macosx> > </rootFolders> > </product> > {code} > And to use tycho 0.23-snapshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19985) Tooltips in Central get stuck easily

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19985?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-19985: ---------------------------------- Description: When I opened Central today, the tooltip over the first project in Central got shown (after I hovered my mouse over) and subsequently it would get stuck there and other tooltips would show up over it. Radim said this happened in your demo also, so I think you know this bug. (It seems there is no JIRA yet.) I tried to replicate this several times, always closing and opening Central, and I was able to replicate every time. You just need to hover your mouse over the items pretty quickly and sooner or later one of the tooltips will get stuck. !central-tooltips.png! was: When I opened Central today, the tooltip over the first project in Central got shown (after I hovered my mouse over) and subsequently it would get stuck there and other tooltips would show up over it. Radim said this happened in your demo also, so I think you know this bug. (It seems there is no JIRA yet.) I tried to replicate this several times, always closing and opening Central, and I was able to replicate every time. You just need to hover your mouse over the items pretty quickly and sooner or later one of the tooltips will get stuck. > Tooltips in Central get stuck easily > ------------------------------------ > > Key: JBIDE-19985 > URL: https://issues.jboss.org/browse/JBIDE-19985 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Priority: Minor > Attachments: central-tooltips.png > > > When I opened Central today, the tooltip over the first project in Central got shown (after I hovered my mouse over) and subsequently it would get stuck there and other tooltips would show up over it. > Radim said this happened in your demo also, so I think you know this bug. (It seems there is no JIRA yet.) > I tried to replicate this several times, always closing and opening Central, and I was able to replicate every time. You just need to hover your mouse over the items pretty quickly and sooner or later one of the tooltips will get stuck. > !central-tooltips.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 2015