[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.4.3.AM2
(was: 4.4.3.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
> Fix For: 4.4.3.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)
7 years, 9 months
[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22969:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Make sure OpenShift Tools support proxies
> -----------------------------------------
>
> Key: JBIDE-22969
> URL: https://issues.jboss.org/browse/JBIDE-22969
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Reporter: Alexey Kazakov
> Assignee: Dmitrii Bocharov
> Fix For: 4.4.3.AM2
>
> Attachments: proxy_settings.png, proxy_settings_2.png
>
>
> CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too.
> If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side.
> This issue covers:
> - testing
> - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests)
> - fixing any problems we have in OpenShift tooling regarding proxy support.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (JBIDE-23026) Integration tests: improve test stability
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23026?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23026:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Integration tests: improve test stability
> -----------------------------------------
>
> Key: JBIDE-23026
> URL: https://issues.jboss.org/browse/JBIDE-23026
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: integration_tests
> Fix For: 4.4.3.AM2
>
>
> There are several impediments to the test stability:
> * tests dont set up their env individually
> * some tests assert the oc binary, but this binary is not the same across platforms (oc, oc.exe, etc): org.jboss.tools.openshift.reddeer.requirement.OCBinary et org.jboss.tools.openshift.reddeer.utils.OpenShiftLabel
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (JBIDE-23625) JMX: jmx tree is not very usable
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.4.3.AM2
(was: 4.4.3.AM1)
> JMX: jmx tree is not very usable
> --------------------------------
>
> 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
> Fix For: 4.4.3.AM2
>
> 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:
> !mbean-deployment.png!
> Rather painfull to find a listing of your deployments in this way.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months