June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23279) Exception generated when OS 3 connection URL is invalid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23279?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23279: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > Exception generated when OS 3 connection URL is invalid > ------------------------------------------------------- > > Key: JBIDE-23279 > URL: https://issues.jboss.org/browse/JBIDE-23279 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.x > > > EXEC: launch application wizard via file menu: New > OpenShift > OpenShift application > EXEC: select <New Connection> > EXEC: enter invalid URL in the host field > ASSERT: an com.openshift.restclient.OpenShiftException: Unable to initialize client exception is logged into the console -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23270) [Watcher] Deploy docker wizard: pushing image to OpenShift Docker registry refused because of self-signed certificate

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23270?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23270: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > [Watcher] Deploy docker wizard: pushing image to OpenShift Docker registry refused because of self-signed certificate > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23270 > URL: https://issues.jboss.org/browse/JBIDE-23270 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Labels: deploy_docker_wizard, upstream > Fix For: 4.5.0.AM2 > > Attachments: pushing-failed-self-signed-certificate.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23403) As a user I need to be able to inspect the state of my EAP deployments

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23403?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23403: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > As a user I need to be able to inspect the state of my EAP deployments > ---------------------------------------------------------------------- > > Key: JBIDE-23403 > URL: https://issues.jboss.org/browse/JBIDE-23403 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: openshift_v3, server, web_console > Fix For: 4.5.x > > > The web console for eap was disabled in the eap image that we have in OpenShift. It's therefore not possible for users to inspect the state of their deployment. > The only there is to do such thing is to inspect jolokia informations. There is no such tooling in Eclipse yet. Furthermore the url to access those is non-obvious as one can see [here|http://developers.redhat.com/blog/2016/03/30/jolokia-jvm-monitoring-...]. I therefore suggest that we should provide help/tooling that allows users to easily access and manipulate those informations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23434) Preferences: allow loading & validating old ssl certificates that were stored in default locale

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23434?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-23434. ------------------------------------ Nothing for QE to verify here. Closing. > Preferences: allow loading & validating old ssl certificates that were stored in default locale > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23434 > URL: https://issues.jboss.org/browse/JBIDE-23434 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM1 > > > In JBIDE-23208 we noticed that ssl certificates were store in system default locale to the preferences. The fix fixated the locale to english. We should allow loading and migrating these old certificates. See https://github.com/jbosstools/jbosstools-openshift/pull/1324 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23417) [Tests]Deploy image wizard: Should have integration tests for the "Services & Routing Settings" wizard page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23417?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23417: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > [Tests]Deploy image wizard: Should have integration tests for the "Services & Routing Settings" wizard page > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23417 > URL: https://issues.jboss.org/browse/JBIDE-23417 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Labels: deploy_docker_wizard, integration-test, openshift_v3 > Fix For: 4.5.0.AM2 > > Attachments: services-and-routing-settings-wizard-page.png > > > We should create/add integration tests for the "Services and Routing Settings" wizard page which recently got a new column to set the port for the route added. > !services-and-routing-settings-wizard-page.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23434) Preferences: allow loading & validating old ssl certificates that were stored in default locale

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23434?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-23434. -------------------------------------- Resolution: Rejected The way we store certificates was changed completely in JBIDE-24312. We dont use locales any more, we store the raw data. It was not possible to properly migrate the existing (incomplete) certificates to the new facility. We thus decided to use a new storage facility and drop the existing ones. This issue is thus no issue any more. > Preferences: allow loading & validating old ssl certificates that were stored in default locale > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23434 > URL: https://issues.jboss.org/browse/JBIDE-23434 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM1 > > > In JBIDE-23208 we noticed that ssl certificates were store in system default locale to the preferences. The fix fixated the locale to english. We should allow loading and migrating these old certificates. See https://github.com/jbosstools/jbosstools-openshift/pull/1324 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4419) DevSuite 1.4 Mac Java Installation related Issues

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4419?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4419: ------------------------------ Story Points: 8 > DevSuite 1.4 Mac Java Installation related Issues > ------------------------------------------------- > > Key: JBDS-4419 > URL: https://issues.jboss.org/browse/JBDS-4419 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: Mac OS X 10.10.5, DevSuite 1.4.0 online installer. > Reporter: Robert Terzi > Assignee: Jan Richter > Fix For: 11.0.0.AM2 > > > When trying to run DevSuite 1.4 online installer on Mac OS X 10.10, there are several serious usability problems related to getting Java installed: > # The installer keeps triggering a pop-up to install java. After the pop-up is dismissed is reappears within a few seconds making it difficult to do anything with the install. This appears to be triggered by running /usr/bin/java. So presumably, during the download selection screen, the installer is repeatedly trying to run /usr/bin/java triggering this loop. > # If the user follows the pop-up, and installs Oracle Java, it appears to install a Java SE that works as a plugin in Safari, but /usr/bin/java still triggers no Java installed. (The Java download that results from this is Oracle jre-8u131-macosx-x64.dmg) > # Note: The above means even though the instructions to install Java have been followed, and some version of java has been installed and verified in the browser, the installer has been exited and restarted, the same thing happens again! > # There is a link in the installer to click for Oracle Java, but it's not clear if that link goes to a valid java or the incessant pop-up behavior is preventing that link from working. > # Unselectiong Dev Studio does NOT stop the pop-up from incessantly reoccurring. > This makes for an extremely frustrating user experience. While some of it might be due to Oracle's packaing/terminology around Java, the DevSuite installer appears to be causing the problems. > # This might be related to JBDS-4402, where it appears the installer at least on windows attempts to keep rescanning when window events occur rather than having some sort of flow to cause a rescan. > # I haven't tried other versions of OS X, but at least on 10.10.5, /usr/bin/java causes this problematic pop-up. Suggest the installer find another way of testing if java is installed and what version on Mac OS. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23625) Duplicate nodes in JMX tree makes tree hard to navigate

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23625?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23625: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Duplicate nodes in JMX tree makes tree hard to navigate > ------------------------------------------------------- > > Key: JBIDE-23625 > URL: https://issues.jboss.org/browse/JBIDE-23625 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Labels: jmx, jolokia > Fix For: 4.5.x > > Attachments: image-2016-12-02-16-47-59-519.png > > > steps to reproduce: > # EXEC: create a new app via eap64-basic-s2i template and import the source to a workspace project > # EXEC: create a server adapter for it > # ASSERT: your server adapter now has a JMX child node > # EXEC: double click it and wait until all MBeans are loaded > # EXEC: now try to see if you can find your deployment > Result: > You get a listing of tons of beans. > !mbeans.png! > Your deployment is a child bean of jboss.as, named by the war that was created: > !image-2016-12-02-16-47-59-519.png|thumbnail! > Rather painfull to find a listing of your deployments in this way. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23625) Duplicate nodes in JMX tree makes tree hard to navigate

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23625?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23625: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM2) > Duplicate nodes in JMX tree makes tree hard to navigate > ------------------------------------------------------- > > Key: JBIDE-23625 > URL: https://issues.jboss.org/browse/JBIDE-23625 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Labels: jmx, jolokia > Fix For: 4.5.x > > Attachments: image-2016-12-02-16-47-59-519.png > > > steps to reproduce: > # EXEC: create a new app via eap64-basic-s2i template and import the source to a workspace project > # EXEC: create a server adapter for it > # ASSERT: your server adapter now has a JMX child node > # EXEC: double click it and wait until all MBeans are loaded > # EXEC: now try to see if you can find your deployment > Result: > You get a listing of tons of beans. > !mbeans.png! > Your deployment is a child bean of jboss.as, named by the war that was created: > !image-2016-12-02-16-47-59-519.png|thumbnail! > Rather painfull to find a listing of your deployments in this way. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23602) Server adapter: Hot code replace failed dialog has poor usability

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23602?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23602: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Server adapter: Hot code replace failed dialog has poor usability > ----------------------------------------------------------------- > > Key: JBIDE-23602 > URL: https://issues.jboss.org/browse/JBIDE-23602 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM2 > > Attachments: hot-code-replace-failed-2.png > > > steps to reproduce: > # ASSERT: have jboss-helloworld running in OpenShift (create it via eap64-basic-s2i template), the source code for it imported to a workspace project and a server adapter for it > # EXEC: open HelloService and change it to the following: > {code:title=HelloService} > public class HelloService { > private static final String MAGIC_STRING = "42"; > > String createHelloMessage(String name) { > return "Hello " + name + ", the magic string is " + MAGIC_STRING + "!"; > } > } > {code} > and save the editor > Result: > "Hot code replace failed" dialog pops up, which is expected. > !hot-code-replace-failed-2.png! > But it's usability is poor: > * the affected module is not fully shown (half of it cut off) > * there's no margin on the right border of the dialog > * No button is pre-selected so that I can simply hit Return to pick a sane default choice (I have to hit tap to get to the button I want to press or use my mouse). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017