September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20708) tools.jboss.org/features: Add Docker

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20708?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-20708: --------------------------------------- let me work on this by the end of the week. > tools.jboss.org/features: Add Docker > ------------------------------------ > > Key: JBIDE-20708 > URL: https://issues.jboss.org/browse/JBIDE-20708 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Fix For: 4.3.0.Final > > > We should add Docker to tools.jboss.org/features -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20833) Version of playground plugins is CR2 instead of Final

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20833?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20833: ---------------------------------------- [~nickboldt] Could it be that the jbosstools-playground job isn't in the buildflow? Or maybe happening too late (since its bundles get included in other features) ? [~akazakov] Is this a real blocker for the release? > Version of playground plugins is CR2 instead of Final > ----------------------------------------------------- > > Key: JBIDE-20833 > URL: https://issues.jboss.org/browse/JBIDE-20833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, playground > Affects Versions: 4.3.0.CR2 > Reporter: Lucia Jelinkova > Priority: Critical > > All plugins in JBT CR2 build have Final version, except for Easymport: > org.jboss.tools.playground.easymport.jee_1.0.0.CR2-v20150924-2213-B23.jar > org.jboss.tools.playground.easymport.maven_1.0.0.CR2-v20150924-2213-B23.jar -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20833) Version of playground plugins is CR2 instead of Final

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-20833: --------------------------------------- Summary: Version of playground plugins is CR2 instead of Final Key: JBIDE-20833 URL: https://issues.jboss.org/browse/JBIDE-20833 Project: Tools (JBoss Tools) Issue Type: Bug Components: easymport, playground Affects Versions: 4.3.0.CR2 Reporter: Lucia Jelinkova Priority: Critical All plugins in JBT CR2 build have Final version, except for Easymport: org.jboss.tools.playground.easymport.jee_1.0.0.CR2-v20150924-2213-B23.jar org.jboss.tools.playground.easymport.maven_1.0.0.CR2-v20150924-2213-B23.jar -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18428) Connection wizard: get "Unknown error" instead of "Authentication error" when using bad credentials (WATCHER)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18428?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18428: ------------------------------------- Labels: connection_wizard openshift_v2 upstream (was: connection_wizard upstream) > Connection wizard: get "Unknown error" instead of "Authentication error" when using bad credentials (WATCHER) > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18428 > URL: https://issues.jboss.org/browse/JBIDE-18428 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift_v2, upstream > Fix For: 4.3.x > > Attachments: unknown-error.png > > > The issues is that OpenShift Online responds with *500 Internal Server Error* when invalid credentials are being used (where *401 Unauthorized* is expect) > {code} > curl -v --user adietish@redhat.com:bogus https://openshift.redhat.com/broker/rest/user* Adding handle: conn: 0xaa8a80 > * Adding handle: send: 0 > * Adding handle: recv: 0 > * Curl_addHandleToPipeline: length: 1 > * - Conn 0 (0xaa8a80) send_pipe: 1, recv_pipe: 0 > * About to connect() to openshift.redhat.com port 443 (#0) > * Trying 50.19.249.93... > * Connected to openshift.redhat.com (50.19.249.93) port 443 (#0) > * Initializing NSS with certpath: sql:/etc/pki/nssdb > * CAfile: /etc/pki/tls/certs/ca-bundle.crt > CApath: none > * SSL connection using TLS_RSA_WITH_AES_128_CBC_SHA > * Server certificate: > * subject: CN=openshift.redhat.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US > * start date: Jul 23 00:00:00 2014 GMT > * expire date: Jul 27 12:00:00 2017 GMT > * common name: openshift.redhat.com > * issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US > * Server auth using Basic with user 'adietish(a)redhat.com' > > GET /broker/rest/user HTTP/1.1 > > Authorization: Basic YWRpZXRpc2hAcmVkaGF0LmNvbTpib2d1cw== > > User-Agent: curl/7.32.0 > > Host: openshift.redhat.com > > Accept: */* > > > < HTTP/1.1 500 > < Cache-Control: no-cache, private > < Content-Type: application/json; charset=utf-8 > < Date: Wed, 24 Sep 2014 10:18:21 GMT > < ProxyTime: D=374659 > * Server Apache/2.2.15 (Red Hat) is not blacklisted > < Server: Apache/2.2.15 (Red Hat) > < Status: 500 > < Strict-Transport-Security: max-age=15768000, includeSubDomains > < Vary: Accept-Encoding,User-Agent > < X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.21 > < X-Rack-Cache: miss > < X-Request-Id: b25500e832d6bbebb1bc7eee5e3175b4 > < X-Runtime: 0.367919 > < X-UA-Compatible: IE=Edge,chrome=1 > < Content-Length: 376 > < Connection: keep-alive > < > * Connection #0 to host openshift.redhat.com left intact > {"api_version":1.7,"data":null,"messages":[{"exit_code":1,"field":null,"index":null,"severity":"error","text":"Unable to authenticate the user. Please try again and contact support if the issue persists. \nReference ID: b25500e832d6bbebb1bc7eee5e3175b4"}],"status":"internal_server_error","supported_api_versions":[1.0,1.1,1.2,1.3,1.4,1.5,1.6,1.7],"type":null,"version":"1.7"} > {code} > stg.openshift.redaht.com is responding with the correct 401: > {code} > [adietish@localhost openshift-java-client]$ curl -v --proxy https://file.rdu.redhat.com:3128 --user adietish@redhat.com:bogus https://stg.openshift.redhat.com/broker/rest/user > * Adding handle: conn: 0x178dae0 > * Adding handle: send: 0 > * Adding handle: recv: 0 > * Curl_addHandleToPipeline: length: 1 > * - Conn 0 (0x178dae0) send_pipe: 1, recv_pipe: 0 > * About to connect() to proxy file.rdu.redhat.com port 3128 (#0) > * Trying 10.11.5.7... > * Connected to file.rdu.redhat.com (10.11.5.7) port 3128 (#0) > * Establish HTTP proxy tunnel to stg.openshift.redhat.com:443 > * Server auth using Basic with user 'adietish(a)redhat.com' > > CONNECT stg.openshift.redhat.com:443 HTTP/1.1 > > Host: stg.openshift.redhat.com:443 > > User-Agent: curl/7.32.0 > > Proxy-Connection: Keep-Alive > > > < HTTP/1.0 200 Connection established > < > * Proxy replied OK to CONNECT request > * Initializing NSS with certpath: sql:/etc/pki/nssdb > * CAfile: /etc/pki/tls/certs/ca-bundle.crt > CApath: none > * SSL connection using TLS_DHE_RSA_WITH_AES_256_CBC_SHA > * Server certificate: > * subject: CN=stg.openshift.redhat.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US > * start date: Apr 30 00:00:00 2014 GMT > * expire date: May 04 12:00:00 2016 GMT > * common name: stg.openshift.redhat.com > * issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US > * Server auth using Basic with user 'adietish(a)redhat.com' > > GET /broker/rest/user HTTP/1.1 > > Authorization: Basic YWRpZXRpc2hAcmVkaGF0LmNvbTpib2d1cw== > > User-Agent: curl/7.32.0 > > Host: stg.openshift.redhat.com > > Accept: */* > > > < HTTP/1.1 401 > < Date: Wed, 24 Sep 2014 10:19:22 GMT > * Server Apache/2.2.15 (Red Hat) is not blacklisted > < Server: Apache/2.2.15 (Red Hat) > < X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.21 > * Authentication problem. Ignoring this. > < WWW-Authenticate: Basic realm="Application" > < X-UA-Compatible: IE=Edge,chrome=1 > < Cache-Control: no-cache, private > < X-Request-Id: 5217138e18f0e036b1880d006e4c3cb6 > < X-Runtime: 0.569233 > < X-Rack-Cache: miss > < Status: 401 > < Content-Length: 27 > < Content-Type: text/html; charset=utf-8 > < Vary: Accept-Encoding,User-Agent > < Strict-Transport-Security: max-age=15768000, includeSubDomains > < ProxyTime: D=574882 > < > HTTP Basic: Access denied. > * Connection #0 to host file.rdu.redhat.com left intact > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20716) Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 in New Connection dialog trigger usage of default server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20716?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20716: ------------------------------------- Summary: Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 in New Connection dialog trigger usage of default server (was: Switch from OpenShift 3 server type to OpenShift 2 in New Connection dialog trigger usage of default server) > Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 in New Connection dialog trigger usage of default server > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20716 > URL: https://issues.jboss.org/browse/JBIDE-20716 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Final > > > In a New Connection dialog if OpenShift 3 server type is selected and there is no server URL then switch to OpenShift 2 server type checks (enables) the Use default Server checkbox. We should have consistent behavior in switching between OpenShift 2 and OpenShift 3. Because if there is a server URL for OpenShift X server type and I switch to OpenShift Y server type, the URL value persists and checkbox is not being checked. > We should not check the Use default Server check box upon switching from OpenShift 3 to OpenShift 2 server type with empty URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20716) Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 in New Connection dialog trigger usage of default server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20716?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20716: ------------------------------------- Labels: connection_wizard (was: ) > Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 in New Connection dialog trigger usage of default server > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20716 > URL: https://issues.jboss.org/browse/JBIDE-20716 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Final > > > In a New Connection dialog if OpenShift 3 server type is selected and there is no server URL then switch to OpenShift 2 server type checks (enables) the Use default Server checkbox. We should have consistent behavior in switching between OpenShift 2 and OpenShift 3. Because if there is a server URL for OpenShift X server type and I switch to OpenShift Y server type, the URL value persists and checkbox is not being checked. > We should not check the Use default Server check box upon switching from OpenShift 3 to OpenShift 2 server type with empty URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19095) Console: All env. vars are listed as "Snapshot Restore/Deploy for application ..."

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19095?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19095: ------------------------------------- Labels: environment_variables openshift_v2 (was: environment_variables) > Console: All env. vars are listed as "Snapshot Restore/Deploy for application ..." > ---------------------------------------------------------------------------------- > > Key: JBIDE-19095 > URL: https://issues.jboss.org/browse/JBIDE-19095 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: environment_variables, openshift_v2 > Fix For: 4.3.x > > Attachments: erroneous-snapshot-restore-title.png > > > While having an application on OpenShift and listing all environment variable on it, there is incorrect label in ConsoleView. While choosing specific console, the listed environment variables for specific application are labeled there as "Snapshot Restore/Deploy for application ... (domainname):". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20716) Switch from OpenShift 3 server type to OpenShift 2 in New Connection dialog trigger usage of default server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20716?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-20716: ---------------------------------------- Assignee: (was: Andre Dietisheim) > Switch from OpenShift 3 server type to OpenShift 2 in New Connection dialog trigger usage of default server > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20716 > URL: https://issues.jboss.org/browse/JBIDE-20716 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.3.1.Final > > > In a New Connection dialog if OpenShift 3 server type is selected and there is no server URL then switch to OpenShift 2 server type checks (enables) the Use default Server checkbox. We should have consistent behavior in switching between OpenShift 2 and OpenShift 3. Because if there is a server URL for OpenShift X server type and I switch to OpenShift Y server type, the URL value persists and checkbox is not being checked. > We should not check the Use default Server check box upon switching from OpenShift 3 to OpenShift 2 server type with empty URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19095) Console: All env. vars are listed as "Snapshot Restore/Deploy for application ..."

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19095?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19095: ------------------------------------- Summary: Console: All env. vars are listed as "Snapshot Restore/Deploy for application ..." (was: OpenShift show all env. vars in Console view are listed as "Snapshot Restore/Deploy for application ...") > Console: All env. vars are listed as "Snapshot Restore/Deploy for application ..." > ---------------------------------------------------------------------------------- > > Key: JBIDE-19095 > URL: https://issues.jboss.org/browse/JBIDE-19095 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: environment_variables > Fix For: 4.3.x > > Attachments: erroneous-snapshot-restore-title.png > > > While having an application on OpenShift and listing all environment variable on it, there is incorrect label in ConsoleView. While choosing specific console, the listed environment variables for specific application are labeled there as "Snapshot Restore/Deploy for application ... (domainname):". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20686) Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20686?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20686: ------------------------------------- Labels: openshift_v3 preferences (was: ) > Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-20686 > URL: https://issues.jboss.org/browse/JBIDE-20686 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, preferences > Fix For: 4.3.x > > > In OpenShift 3 workbench preference page restoring default setting by clicking on a button Restore Defaults pops up a warning dialog with title "No OpenShift Client binary" and text "Could not find the OpenShift binary "oc" on your path". I would expect that choosing default settings would just clear text field with oc binary location and no dialog is shown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 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 September 2015