[JBoss JIRA] (JBIDE-18459) MacBook Pro Retina Display Font
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18459?page=com.atlassian.jira.plugi... ]
Burr Sutter updated JBIDE-18459:
--------------------------------
Attachment: Screenshot 2014-09-30 14.04.34.png
> MacBook Pro Retina Display Font
> -------------------------------
>
> Key: JBIDE-18459
> URL: https://issues.jboss.org/browse/JBIDE-18459
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Affects Versions: 4.2.0.CR1
> Environment: MacBook Pro 15" mid-2014 Retina set at "Best for Display" (default)
> Reporter: Burr Sutter
> Attachments: Screenshot 2014-09-30 13.58.59.png, Screenshot 2014-09-30 14.04.34.png
>
>
> Some fonts are "fuzzy".
> Screenshot 1
> - under "JBoss Buzz"
> - under "Start from a sample" and Portal Applications
> - the open cheatsheet.xml (AngularJS Forge)
> Screenshot 2
> - jQuery Mobile and Ionic Palettes
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18459) MacBook Pro Retina Display Font
by Burr Sutter (JIRA)
Burr Sutter created JBIDE-18459:
-----------------------------------
Summary: MacBook Pro Retina Display Font
Key: JBIDE-18459
URL: https://issues.jboss.org/browse/JBIDE-18459
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 4.2.0.CR1
Environment: MacBook Pro 15" mid-2014 Retina set at "Best for Display" (default)
Reporter: Burr Sutter
Some fonts are "fuzzy".
Screenshot 1
- under "JBoss Buzz"
- under "Start from a sample" and Portal Applications
- the open cheatsheet.xml (AngularJS Forge)
Screenshot 2
- jQuery Mobile and Ionic Palettes
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18454) Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18454:
---------------------------------------------
How about Oracle Java 8 ?
> Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18454
> URL: https://issues.jboss.org/browse/JBIDE-18454
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.2.0.CR2
>
> Attachments: ssl-error-on-connect.png
>
>
> In https://bugzilla.redhat.com/show_bug.cgi?id=1145848 openshift-java-client cant connect to OpenShift running on RHEL 6.6 when using openjdk. We have to verify that this affects the Eclipse based tooling (that's also using openshift-java-client)
> {code}
> java.io.IOException: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair
> at hudson.plugins.openshift.OpenShiftCloud.getOpenShiftConnection(OpenShiftCloud.java:186)
> at hudson.plugins.openshift.OpenShiftCloud.getSlaves(OpenShiftCloud.java:877)
> at hudson.plugins.openshift.OpenShiftCloud.provisionSlave(OpenShiftCloud.java:451)
> at hudson.plugins.openshift.OpenShiftCloud.provision(OpenShiftCloud.java:413)
> at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:281)
> at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:51)
> at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:368)
> at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-17619) Console for remote server disappears when workspace is switched
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17619?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17619:
---------------------------------------------
what causes rse.ui to load in the first case ? the server wizard ?
> Console for remote server disappears when workspace is switched
> ---------------------------------------------------------------
>
> Key: JBIDE-17619
> URL: https://issues.jboss.org/browse/JBIDE-17619
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR2
>
>
> This happened to me today. I created a remote server (EAP 6.2, management, no runtime) and when I started it, I saw the console output for the server. But after some more tinkering with it, the console suddenly stopped appearing (I had the console view open). Not even IDE restart helped.
> The only thing that helped me here was to delete the server and create a new one.
> I think I have a way to reproduce this - it actually happens when you create the server, then switch to a new workspace, then back again.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-17619) Console for remote server disappears when workspace is switched
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17619?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17619:
-------------------------------------
The host shell listener is contributed by our rse.ui plugin. The activator of our rse.ui plugin registers a host-shell listener with RSEHostShellModel, a class we own in our rse.core plugin, to send the messages to the console view. If our rse.ui plugin has not yet been started, the listener is not registered.
This was not replicatable for me because the server editor was open on workspace restart, and the server editor forced the loading of our rse.ui plugin to display various widgets. This meant that rse.ui was always started before I got to start the server, and so the listener was always registered, and the console always loaded.
The real question now is when to start rse.ui plugin, or how to force it starting and at what time is most appropriate.
Workaround: Open the server editor. The console will begin showing updates.
> Console for remote server disappears when workspace is switched
> ---------------------------------------------------------------
>
> Key: JBIDE-17619
> URL: https://issues.jboss.org/browse/JBIDE-17619
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR2
>
>
> This happened to me today. I created a remote server (EAP 6.2, management, no runtime) and when I started it, I saw the console output for the server. But after some more tinkering with it, the console suddenly stopped appearing (I had the console view open). Not even IDE restart helped.
> The only thing that helped me here was to delete the server and create a new one.
> I think I have a way to reproduce this - it actually happens when you create the server, then switch to a new workspace, then back again.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18458) Keep ionic libs up to date
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-18458:
--------------------------------------
Summary: Keep ionic libs up to date
Key: JBIDE-18458
URL: https://issues.jboss.org/browse/JBIDE-18458
Project: Tools (JBoss Tools)
Issue Type: Task
Components: jsp/jsf/xml/html source editing
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 4.2.1.Final
We should update our JS/CSS links in ionic palette for next JBT release.
We still need to support bower not to update the libs manually but until JBIDE-17943 is fixed we have to do it.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-17619) Console for remote server disappears when workspace is switched
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17619?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17619:
-------------------------------------
As for why show-in -> console is grey, I'd like to point out https://bugs.eclipse.org/bugs/show_bug.cgi?id=431910
The show in console action is contributed by WTP and requires an IProcess. I did not do any work to create an IProcess for a remote server, and so I could not hook up our remote server impl to the remote IProcess action. Instead we manually make a console and send text to it.
So basically show in -> console doesn't work for our remote servers.
> Console for remote server disappears when workspace is switched
> ---------------------------------------------------------------
>
> Key: JBIDE-17619
> URL: https://issues.jboss.org/browse/JBIDE-17619
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR2
>
>
> This happened to me today. I created a remote server (EAP 6.2, management, no runtime) and when I started it, I saw the console output for the server. But after some more tinkering with it, the console suddenly stopped appearing (I had the console view open). Not even IDE restart helped.
> The only thing that helped me here was to delete the server and create a new one.
> I think I have a way to reproduce this - it actually happens when you create the server, then switch to a new workspace, then back again.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18454) Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18454:
------------------------------------------
I tested with openjdk 1.7 and sun jdk in 1.6 & 1.7. All fail with the above stacktrace.
> Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18454
> URL: https://issues.jboss.org/browse/JBIDE-18454
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.2.0.CR2
>
> Attachments: ssl-error-on-connect.png
>
>
> In https://bugzilla.redhat.com/show_bug.cgi?id=1145848 openshift-java-client cant connect to OpenShift running on RHEL 6.6 when using openjdk. We have to verify that this affects the Eclipse based tooling (that's also using openshift-java-client)
> {code}
> java.io.IOException: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair
> at hudson.plugins.openshift.OpenShiftCloud.getOpenShiftConnection(OpenShiftCloud.java:186)
> at hudson.plugins.openshift.OpenShiftCloud.getSlaves(OpenShiftCloud.java:877)
> at hudson.plugins.openshift.OpenShiftCloud.provisionSlave(OpenShiftCloud.java:451)
> at hudson.plugins.openshift.OpenShiftCloud.provision(OpenShiftCloud.java:413)
> at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:281)
> at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:51)
> at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:368)
> at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18454) Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18454:
-------------------------------------
Summary: Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair) (was: Cant connect to OpenShift running on RHEL 6.6 when using openjdk (javax.net.ssl.SSLException: Could not generate DH keypair))
> Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18454
> URL: https://issues.jboss.org/browse/JBIDE-18454
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.2.0.CR2
>
> Attachments: ssl-error-on-connect.png
>
>
> In https://bugzilla.redhat.com/show_bug.cgi?id=1145848 openshift-java-client cant connect to OpenShift running on RHEL 6.6 when using openjdk. We have to verify that this affects the Eclipse based tooling (that's also using openshift-java-client)
> {code}
> java.io.IOException: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair
> at hudson.plugins.openshift.OpenShiftCloud.getOpenShiftConnection(OpenShiftCloud.java:186)
> at hudson.plugins.openshift.OpenShiftCloud.getSlaves(OpenShiftCloud.java:877)
> at hudson.plugins.openshift.OpenShiftCloud.provisionSlave(OpenShiftCloud.java:451)
> at hudson.plugins.openshift.OpenShiftCloud.provision(OpenShiftCloud.java:413)
> at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:281)
> at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:51)
> at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:368)
> at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months