[JBoss JIRA] (JBDS-3383) Include Feature Patch for WTP 3.6.3 into JBDS 8.1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3383?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3383:
----------------------------------
Connector description isn't very long - we generally only have a few words. Also, the link won't be clickable. Would be better to use a bit.ly link if you really want something in there.
> Include Feature Patch for WTP 3.6.3 into JBDS 8.1
> -------------------------------------------------
>
> Key: JBDS-3383
> URL: https://issues.jboss.org/browse/JBDS-3383
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 8.1.0.CR1
> Reporter: Victor Rubezhny
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 8.1.0.GA
>
> Attachments: WTP Patches 3.6.3-P.png
>
>
> When the fix for [Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=433515] was made, the WTP 3.6 stream was already closed (it's ended with 3.6 SR2), so the fix was made only for WTP 3.7 stream.
> JSDT Feature Patch was made due to let the users to bring the fix back to their 3.6 SR2 environments. See: [Bug 461160 - Backport the fix for 'Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=461160]
> Can we apply this fix into JBDS 8.1?
> Technically, the Feature Patch installs org.eclipse.wst.jsdt.feature.patch feature that brings fixed org.eclipse.wst.jsdt.core_1.3.301.v201503171857.jar instead of org.eclipse.wst.jsdt.core_1.3.300.v201410221502.jar harmed by the bug.
> Feature Patch is released at The Eclipse Web Tools Platform (WTP) software repository: http://download.eclipse.org/webtools/repository/luna
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3383) Include Feature Patch for WTP 3.6.3 into JBDS 8.1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3383?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3383:
----------------------------------
I haven't done a PR for JBDS.1 above (`include in JBDS core .feature so it's installed by default via installer jar`), because if I use <include>, we will have to *include* this patch feature in any future 8.1.x releases, even if it's replaced by a future WTP 3.6.4 release.
If we use <require> I don't think it'll be installed OOTB, because it'll just be seen as a requirement. Right?
And I can't do the Marketplace ones yet because it's not live in the /stable/ and /8.0/ update sites.
> Include Feature Patch for WTP 3.6.3 into JBDS 8.1
> -------------------------------------------------
>
> Key: JBDS-3383
> URL: https://issues.jboss.org/browse/JBDS-3383
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 8.1.0.CR1
> Reporter: Victor Rubezhny
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 8.1.0.GA
>
> Attachments: WTP Patches 3.6.3-P.png
>
>
> When the fix for [Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=433515] was made, the WTP 3.6 stream was already closed (it's ended with 3.6 SR2), so the fix was made only for WTP 3.7 stream.
> JSDT Feature Patch was made due to let the users to bring the fix back to their 3.6 SR2 environments. See: [Bug 461160 - Backport the fix for 'Bug 433515 - Eclipse freezes every few minutes' into Luna SR2|https://bugs.eclipse.org/bugs/show_bug.cgi?id=461160]
> Can we apply this fix into JBDS 8.1?
> Technically, the Feature Patch installs org.eclipse.wst.jsdt.feature.patch feature that brings fixed org.eclipse.wst.jsdt.core_1.3.301.v201503171857.jar instead of org.eclipse.wst.jsdt.core_1.3.300.v201410221502.jar harmed by the bug.
> Feature Patch is released at The Eclipse Web Tools Platform (WTP) software repository: http://download.eclipse.org/webtools/repository/luna
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19500) warn/inform users running on non-compatilbe JVMs they are loosing out on features
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-19500:
-------------------------------------------
Summary: warn/inform users running on non-compatilbe JVMs they are loosing out on features
Key: JBIDE-19500
URL: https://issues.jboss.org/browse/JBIDE-19500
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Max Rydahl Andersen
while reading https://developer.jboss.org/message/922318?et=watches.email.thread#922318 I got the idea that we could have a startup plugin that detects if the error log has lines matching:
{code}
org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.preferences [1447]
Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))"
{code}
and there by tell them that they need to run JavaSE 1.7 to get this to work.
This dialog should show up and have "don't disturb me again" for the specific bundle/feature that is filtered out.
This is to warn those users that run ecipse with default javavm that still is java 6 on many installs.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19270) Unhandled event loop exception when opening Batch Job Configuration editor
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19270?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-19270:
---------------------------------------
Yes,it helps.
> Unhandled event loop exception when opening Batch Job Configuration editor
> --------------------------------------------------------------------------
>
> Key: JBIDE-19270
> URL: https://issues.jboss.org/browse/JBIDE-19270
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch, upstream
> Affects Versions: 4.3.0.Alpha2
> Reporter: Alexey Kazakov
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.3.0.Alpha2
>
>
> 1. Close all Batch Job Configuration editors
> 2. Open any Batch Job Configuration editor (the Design tab should be opened by default, if not then open that tab and re-open the editor).
> 3. See the log:
> {code}
> java.lang.IllegalArgumentException: Argument not valid
> at org.eclipse.swt.SWT.error(SWT.java:4458)
> at org.eclipse.swt.SWT.error(SWT.java:4392)
> at org.eclipse.swt.SWT.error(SWT.java:4363)
> at org.eclipse.swt.graphics.Image.init(Image.java:1294)
> at org.eclipse.swt.graphics.Image.<init>(Image.java:200)
> at org.eclipse.ui.forms.widgets.Section.onPaint(Section.java:344)
> at org.eclipse.ui.forms.widgets.ExpandableComposite$1.paintControl(ExpandableComposite.java:561)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:230)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1437)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1422)
> at org.eclipse.swt.widgets.Control.gtk_draw(Control.java:3212)
> at org.eclipse.swt.widgets.Canvas.gtk_draw(Canvas.java:171)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2085)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5563)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4712)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9174)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
> at org.eclipse.swt.internal.gtk.OS._gdk_window_process_all_updates(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gdk_window_process_all_updates(OS.java:5980)
> at org.eclipse.swt.widgets.Display.update(Display.java:4665)
> at org.eclipse.swt.widgets.Display.runDeferredLayouts(Display.java:3844)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3415)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19270) Unhandled event loop exception when opening Batch Job Configuration editor
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19270?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-19270 at 3/23/15 4:25 PM:
------------------------------------------------------------------------
[~snjeza], you explicitly fix exception in Section.onPaint(). Does that also help with the other exception in my comment of 18/Feb/15?
Use case is described in https://bugs.eclipse.org/bugs/show_bug.cgi?id=460286#c2
was (Author: scabanovich):
[~snjeza], you explicitly fix exception in Section.onPaint(). Does that also help with the other exception in my comment of 18/Feb/15?
> Unhandled event loop exception when opening Batch Job Configuration editor
> --------------------------------------------------------------------------
>
> Key: JBIDE-19270
> URL: https://issues.jboss.org/browse/JBIDE-19270
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch, upstream
> Affects Versions: 4.3.0.Alpha2
> Reporter: Alexey Kazakov
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.3.0.Alpha2
>
>
> 1. Close all Batch Job Configuration editors
> 2. Open any Batch Job Configuration editor (the Design tab should be opened by default, if not then open that tab and re-open the editor).
> 3. See the log:
> {code}
> java.lang.IllegalArgumentException: Argument not valid
> at org.eclipse.swt.SWT.error(SWT.java:4458)
> at org.eclipse.swt.SWT.error(SWT.java:4392)
> at org.eclipse.swt.SWT.error(SWT.java:4363)
> at org.eclipse.swt.graphics.Image.init(Image.java:1294)
> at org.eclipse.swt.graphics.Image.<init>(Image.java:200)
> at org.eclipse.ui.forms.widgets.Section.onPaint(Section.java:344)
> at org.eclipse.ui.forms.widgets.ExpandableComposite$1.paintControl(ExpandableComposite.java:561)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:230)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1437)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1422)
> at org.eclipse.swt.widgets.Control.gtk_draw(Control.java:3212)
> at org.eclipse.swt.widgets.Canvas.gtk_draw(Canvas.java:171)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2085)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5563)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4712)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9174)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
> at org.eclipse.swt.internal.gtk.OS._gdk_window_process_all_updates(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gdk_window_process_all_updates(OS.java:5980)
> at org.eclipse.swt.widgets.Display.update(Display.java:4665)
> at org.eclipse.swt.widgets.Display.runDeferredLayouts(Display.java:3844)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3415)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years