[JBoss JIRA] (JBIDE-19270) Unhandled event loop exception when opening Batch Job Configuration editor
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19270?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-19270:
----------------------------------------
That was fast :) Thank you [~snjeza].
Let's wait for the next Eclipse build to verify the issue is solved.
> 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] (JBDS-3383) Include Feature Patch for WTP 3.6.3 into JBDS 8.1
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3383?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3383:
-------------------------------------
Should work (I didn't test it). I guess we should add only patch feature id into list of IU's, because wst.jsdt.feature.group is already included into JBDS BYOE feature.
> 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-18772) Include publish.sh in parent pom as versioned maven dependency
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18772:
------------------------------------
{quote} This approach makes that we'll slowly prefer avoiding JOB_NAME and other Jenkins property in favor of properties that are inside the pom directly.{quote}
How would the jbosstools-server_master job know where to publish, then, if not using JOB_NAME? What property would you use?
Maybe $\{project.artifactId}_$\{jbosstools_site_stream} = server.all_master ?
Or $\{project.artifactId}_$\{project.parent.version} = server.all_4.2.3.Final-SNAPSHOT ?
If we push a call to rsync.sh into the parent pom for all projects that use the parent pom, we might want to wrap that with a profile so that local builds don't attempt to deploy. Or so that other projects that use the parent pom (like jbosstools-discovery) don't try to deploy accidentally. Does that make sense?
> Include publish.sh in parent pom as versioned maven dependency
> --------------------------------------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.3.0.Alpha2
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19501) Cutted text on features page
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19501?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-19501 at 3/24/15 10:54 AM:
--------------------------------------------------------------
Could not reproduce on Win8.1 w/ Chrome 41.0.2272.101 m
http://snag.gy/8jztl.jpg
Could not reproduce on Fedora 20 w/ Firefox 33.1 ( Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 ):
[^19501_1.png]
[^19501_2.png]
Could not reproduce on Fedora 20 w/ Chrome 39.0.2171.71 (64-bit):
[^19501_3_Chrome.png]
*Could reproduce* on Win 8.1 w/ Firefox 34.0.5 ( Windows NT 6.3; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0 ):
http://snag.gy/sgCmr.jpg
was (Author: nickboldt):
Could not reproduce on Win8.1 w/ Chrome 41.0.2272.101 m
http://snag.gy/8jztl.jpg
Could not reproduce on Fedora 20 w/ Firefox 33.1 ( Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 ):
[^19501_1.png]
[^19501_2.png]
Could not reproduce on Fedora 20 w/ Chrome 39.0.2171.71 (64-bit):
[^19501_3_Chrome.png]
*Could reproduce* on Win 8.1 w/ Firefox:
http://snag.gy/sgCmr.jpg
> Cutted text on features page
> ----------------------------
>
> Key: JBIDE-19501
> URL: https://issues.jboss.org/browse/JBIDE-19501
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: website
> Environment: Win 7, Firefox 36.0.1
> Reporter: Konstantin Marmalyukov
> Attachments: 19501_1.png, 19501_2.png, 19501_3_Chrome.png, Screenshot 2015-03-24 13.12.13.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBTIS-415) Productize JBDSIS 8.0.1/JBTIS 4.2.1
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-415:
--------------------------------
Summary: Productize JBDSIS 8.0.1/JBTIS 4.2.1
Key: JBTIS-415
URL: https://issues.jboss.org/browse/JBTIS-415
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: distribution
Reporter: Paul Leacu
Assignee: Paul Leacu
Fix For: 8.0.0.CR1, 4.2.1.CR1
Productize JBDSIS/ JBTIS in jbosstools-download and jbdevstudio.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
