[JBoss JIRA] (JBIDE-18483) For JBIDE 4.2.0.CR2: Prepare for CR2 release [LiveReload]
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18483?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-18483.
-------------------------------
> For JBIDE 4.2.0.CR2: Prepare for CR2 release [LiveReload]
> ---------------------------------------------------------
>
> Key: JBIDE-18483
> URL: https://issues.jboss.org/browse/JBIDE-18483
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: livereload
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR2
>
>
> For JBIDE 4.2.0.CR2 [LiveReload]: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA.
> [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT
> mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT
> {code}
> 5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*:
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18517) On RHEL, JBDS/JBT users must install package webkitgtk to be able to use BrowserSim
by Len DiMaggio (JIRA)
Len DiMaggio created JBIDE-18517:
------------------------------------
Summary: On RHEL, JBDS/JBT users must install package webkitgtk to be able to use BrowserSim
Key: JBIDE-18517
URL: https://issues.jboss.org/browse/JBIDE-18517
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: browsersim
Affects Versions: 4.2.0.CR2
Environment: RHEL 6.5, Oracle 1.7, webkitgtk NOT installed, BrowserSim configured to use GTK2
Reporter: Len DiMaggio
The error returned to the user is:
BrowserSim has failed to start with the following error:
"To use BrowserSim please install webkitgtk 1.2.0 or higher or run BrowserSim with Oracle Java 7u7 and higher."
Also see <a href="http://tools.jboss.org/documentation/faq/browsersim.html">BrowserSim FAQ</a>.
Stack trace:
org.eclipse.swt.SWTError: To use BrowserSim please install webkitgtk 1.2.0 or higher or run BrowserSim with Oracle Java 7u7 and higher.
at org.jboss.tools.vpe.browsersim.BrowserSimRunner.main(BrowserSimRunner.java:78)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-3152) Cheatsheet crashes silently when they need to open files
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-3152?page=com.atlassian.jira.plugin.... ]
Snjezana Peco commented on JBDS-3152:
-------------------------------------
[~rhopp], have you tested in a new workspace?
The JBoss perspective creates an invalid UI part that can't be restored by reseting the perspective.
> Cheatsheet crashes silently when they need to open files
> --------------------------------------------------------
>
> Key: JBDS-3152
> URL: https://issues.jboss.org/browse/JBDS-3152
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Environment: JBDS 8.0.0.CR1b, OSX 10.9.4
> Reporter: Fred Bricon
> Assignee: Snjezana Peco
> Priority: Blocker
>
> After creating a AngularJS Forge project, the cheatsheet opens, then, after clicking a couple times on the continue buttons, persistence.xml opens but the cheatsheet closes silently. The log shows :
> {quote}
> org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:783)
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:573)
> at org.eclipse.swt.widgets.Control.setCursor(Control.java:3659)
> at org.eclipse.ui.internal.cheatsheets.views.CheatSheetViewer.runSubItemPerformExecutable(CheatSheetViewer.java:1096)
> at org.eclipse.ui.internal.cheatsheets.views.CoreItem$4.linkActivated(CoreItem.java:198)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:199)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> {quote}
> It used to work at some point, last week.
--
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 edited comment on JBIDE-18454 at 10/6/14 1:45 PM:
-------------------------------------------------------------------
We decided to provide a flag to turn cipher filtering on and of. The library now provides a system property
{code}
-Ddisable_bad_sslciphers=yes|no|auto
{code}
The default for the system property is *no*
You can set this by system property
{code}
System.setProperty("disable_bad_sslciphers", "yes")
{code}
or by client configuration class
{code}
configuration.setDisableBadSSLCiphers(ConfigurationOptions.YES)
{code}
or in express.conf
disable_bad_sslciphers=yes
{code}
was (Author: adietish):
We decided to provide a flag to turn cipher filtering on and of. The library now provides a system property
{code}
-Ddisable_bad_sslciphers=yes|no|auto
{code}
The default for the system property is *no*
> 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 jdks (openjdk and sun) < 1.8 on linux. 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 edited comment on JBIDE-18454 at 10/6/14 1:45 PM:
-------------------------------------------------------------------
We decided to provide a flag to turn cipher filtering on and of. The library now provides a system property
{code}
-Ddisable_bad_sslciphers=yes|no|auto
{code}
The default for the system property is *no*
You can set this by system property
{code}
System.setProperty("disable_bad_sslciphers", "yes")
{code}
or by client configuration class
{code}
configuration.setDisableBadSSLCiphers(ConfigurationOptions.YES)
{code}
or in express.conf
{code}
disable_bad_sslciphers=yes
{code}
was (Author: adietish):
We decided to provide a flag to turn cipher filtering on and of. The library now provides a system property
{code}
-Ddisable_bad_sslciphers=yes|no|auto
{code}
The default for the system property is *no*
You can set this by system property
{code}
System.setProperty("disable_bad_sslciphers", "yes")
{code}
or by client configuration class
{code}
configuration.setDisableBadSSLCiphers(ConfigurationOptions.YES)
{code}
or in express.conf
disable_bad_sslciphers=yes
{code}
> 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 jdks (openjdk and sun) < 1.8 on linux. 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