October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23208) SSLCertificatesPreference.isValid(String): Could not parse

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23208?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23208: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.2.AM2) > SSLCertificatesPreference.isValid(String): Could not parse > ---------------------------------------------------------- > > Key: JBIDE-23208 > URL: https://issues.jboss.org/browse/JBIDE-23208 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.4.2.AM1 > Reporter: Martin Malina > Fix For: 4.4.x > > > When I start CDK and OpenShift connection is established, I get this in the Error Log view: > org.jboss.tools.openshift.ui > SSLCertificatesPreference.isValid(String): Could not parse 'Čt, 20 Zář 2018 12:54:07' in format E, d MMM yyyy HH:mm:ss > An exception stack trace is not available. > As you can see, the date is localized. I think this started happening after I updated to macOS Sierra last night - I never noticed it before. If we can figure out where the parsing is happening, perhaps we can come up with a switch for using english date here. > Env: > devstudio-10.2.0.AM1-v20160920-0457-B6061-installer-standalone.jar > cdk 2.2.rc5 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22376) Enable JMX when entering Debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22376: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.2.AM2) > Enable JMX when entering Debug mode > ----------------------------------- > > Key: JBIDE-22376 > URL: https://issues.jboss.org/browse/JBIDE-22376 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Thomas Mäder > Fix For: 4.4.x > > > We need to update the deployment configuration when entering debug mode. It is not entirely clear how to determine that an Openshift Pod has indeed a wildfly/EAP in it and can be reached with remoting-jmx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23154) tests: should have sonar checking our pull requests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23154?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23154: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.2.AM2) > tests: should have sonar checking our pull requests > --------------------------------------------------- > > Key: JBIDE-23154 > URL: https://issues.jboss.org/browse/JBIDE-23154 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.x > > > Sonar being run in the background tends to get forgotten. I'd therefore love to have sonar testing our pull requests. > Docs for the sonar github plugin are here: http://docs.sonarqube.org/display/PLUG/GitHub+Plugin -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23299) Write connection information in .kube/.config file on each login

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23299?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23299: ------------------------------------- Labels: connection openshift_v3 (was: ) > Write connection information in .kube/.config file on each login > ---------------------------------------------------------------- > > Key: JBIDE-23299 > URL: https://issues.jboss.org/browse/JBIDE-23299 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Labels: connection, openshift_v3 > Fix For: 4.4.x > > > Some plugins such as fabric8-maven-plugin requires to have information stored in .kube/.config file to work. > When Openshift connection is done in Eclipse tooling, nothing is written in .kube/.config so the fabric8-maven-plugin is failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23299) Write connection information in .kube/.config file on each login

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23299?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23299: ------------------------------------- Fix Version/s: 4.4.x > Write connection information in .kube/.config file on each login > ---------------------------------------------------------------- > > Key: JBIDE-23299 > URL: https://issues.jboss.org/browse/JBIDE-23299 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Fix For: 4.4.x > > > Some plugins such as fabric8-maven-plugin requires to have information stored in .kube/.config file to work. > When Openshift connection is done in Eclipse tooling, nothing is written in .kube/.config so the fabric8-maven-plugin is failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23352: ---------------------------------- Summary: Deploy Docker Wizard: Default routing port selection need more info for users (was: Deploy Docker Wizard: No port is selected by default to be used for routing) > Deploy Docker Wizard: Default routing port selection need more info for users > ----------------------------------------------------------------------------- > > Key: JBIDE-23352 > URL: https://issues.jboss.org/browse/JBIDE-23352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: no_route_selected.png > > > In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open. > If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening. > !no_route_selected.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: No port is selected by default to be used for routing

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23352: ---------------------------------- Description: In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open. If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening. !no_route_selected.png! was: In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default and thus finishing the wizard as it is result into an routing with no mapped port (but by default OpenShift know what to open. If there is only one port mapping, we should check it by default. If there are more port mappings, we should use some heuristics to check it. !no_route_selected.png! > Deploy Docker Wizard: No port is selected by default to be used for routing > --------------------------------------------------------------------------- > > Key: JBIDE-23352 > URL: https://issues.jboss.org/browse/JBIDE-23352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: no_route_selected.png > > > In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open. > If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening. > !no_route_selected.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: No port is selected by default to be used for routing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23352: ------------------------------------- Fix Version/s: 4.4.2.AM2 > Deploy Docker Wizard: No port is selected by default to be used for routing > --------------------------------------------------------------------------- > > Key: JBIDE-23352 > URL: https://issues.jboss.org/browse/JBIDE-23352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: no_route_selected.png > > > In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default and thus finishing the wizard as it is result into an routing with no mapped port (but by default OpenShift know what to open. > If there is only one port mapping, we should check it by default. If there are more port mappings, we should use some heuristics to check it. > !no_route_selected.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ] Xavier Coulon commented on JBDS-3903: ------------------------------------- [~mhusnain], Sorry for the delay in my response. Regarding the prerequisites item, you may want to remove the reference to 'boot2docker' since it has been deprecated for quite some time now. Also, I would suggest that you mention (or clarify) that Red Hat Development Suite ships with CDK which includes Docker but users can install Docker on their host (Linux, Windows or macOS) if they want to use Docker outside of CDK. > Platform Installer does not Setup Docker Env-Vars > ------------------------------------------------- > > Key: JBDS-3903 > URL: https://issues.jboss.org/browse/JBDS-3903 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: docker > Affects Versions: 10.0.0.Alpha1 > Environment: Windows > Reporter: Thomas Mäder > Assignee: Xavier Coulon > Fix For: 10.2.0.AM3 > > > I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection. > Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection. > As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ] Xavier Coulon updated JBDS-3903: -------------------------------- Fix Version/s: 10.2.0.AM3 (was: 10.2.0.AM2) > Platform Installer does not Setup Docker Env-Vars > ------------------------------------------------- > > Key: JBDS-3903 > URL: https://issues.jboss.org/browse/JBDS-3903 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: docker > Affects Versions: 10.0.0.Alpha1 > Environment: Windows > Reporter: Thomas Mäder > Assignee: Xavier Coulon > Fix For: 10.2.0.AM3 > > > I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection. > Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection. > As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016