[JBoss JIRA] (JBIDE-13411) JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13411:
---------------------------------------------
[~mickael_istria] you wrote "That shows dependency resolution is the bottleneck of this job.", I assume you meant "is *not* the bottleneck", right ?
Also note that the tests are not taking anywhere near 8 hrs when run locally so its also affected by jenkins environment; using nio solves nothing here IMO.
Talking with tycho guys they pointed out that surefire tests currently resolve TP twice - one at build startup and secondly for calculating TP per test run.
Again a reason to look at being able to run tests against an existing eclipse install to avoid overhead of TP calculation.
> JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13411
> URL: https://issues.jboss.org/browse/JBIDE-13411
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, Visual Page Editor Templates
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.1.x
>
> Attachments: tests-vs-tycho-build-time.png
>
>
> On a good day, tests will run and all pass in under 4hrs.
> On a grey day, tests will have failures but complete in under 6hrs.
> On a bad day, tests will stall out and the job will fail when it hits its duration upper limit of 8hrs.
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> Surely some of these tests are:
> a) integration, not unit test, and should be relocated to https://github.com/jbosstools/jbosstools-integration-tests/ and run as part of a new job like https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... ?
> b) reliant on UI which is blocking, and should therefore be rewritten so as to not block test execution?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13411) JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13411:
---------------------------------------------
integration-tets repo is just for QE - it is not buildable on its own thus not useful for us for CI builds. Thus moving them to integration-tests is not a good option.
> JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13411
> URL: https://issues.jboss.org/browse/JBIDE-13411
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, Visual Page Editor Templates
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.1.x
>
> Attachments: tests-vs-tycho-build-time.png
>
>
> On a good day, tests will run and all pass in under 4hrs.
> On a grey day, tests will have failures but complete in under 6hrs.
> On a bad day, tests will stall out and the job will fail when it hits its duration upper limit of 8hrs.
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> Surely some of these tests are:
> a) integration, not unit test, and should be relocated to https://github.com/jbosstools/jbosstools-integration-tests/ and run as part of a new job like https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... ?
> b) reliant on UI which is blocking, and should therefore be rewritten so as to not block test execution?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-12976) bump feature/plugin versions in runtime-soa repo
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12976?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-12976.
------------------------------
Resolution: Won't Fix
Since all the contents of this project have been migrated elsewhere, this can be closed WONTFIX.
> bump feature/plugin versions in runtime-soa repo
> ------------------------------------------------
>
> Key: JBIDE-12976
> URL: https://issues.jboss.org/browse/JBIDE-12976
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.0.0.Alpha1-SOA
> Reporter: Nick Boldt
> Assignee: Rob Cernich
> Fix For: 4.0.0.Alpha1-SOA
>
>
> Components in new 4.x master branch in github need to be upversioned so that they're "newer" than the stuff in the 3.3.x branch in SVN. Currently, they are not (in some cases the plugins/features in 3.3.x branch are x.y.2 where the plugins/features in 4.x master are x.y.0).
> Obviously, the stuff in master should be bumped to x.(y+1).0
> You can use this to bump easily:
> {code:title=https://gist.github.com/4548933}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=x.y.z-SNAPSHOT
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBDS-2460) replace included p2-director.zip with upstream version from tycho-standalone-p2-director
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2460?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2460:
----------------------------------
Any reason why this forked code can't move to github instead? [~maxandersen], do you see a reason to keep this internal?
> replace included p2-director.zip with upstream version from tycho-standalone-p2-director
> ----------------------------------------------------------------------------------------
>
> Key: JBDS-2460
> URL: https://issues.jboss.org/browse/JBDS-2460
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rdPartyDependencies, Build, installer
> Affects Versions: 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 7.0.0.Alpha2
>
>
> To build JBDS installer we need p2-director.zip [0], which is 9M and doesn't include sources. Ideally, we could just use something from Eclipse.org at build-time, and COULD include sources.
> [0] https://svn.jboss.org/repos/devstudio/trunk/product/installer/p2-director...
> I looked at tycho-standalone-p2-director [1,2] but it's only an update site -- it lacks equinox.launcher fragments for the various platforms on which we run.
> [1] https://github.com/eclipse/tycho/tree/master/tycho-bundles/tycho-standalo...
> [2] http://search.maven.org/remotecontent?filepath=org/eclipse/tycho/tycho-st...
> So... maybe we need to do something similar but include the binary bits too, so that we can produce something similar to what's in this zip [3] ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13411) JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13411:
------------------------------------
*Unit tests* should be run as part of the project builds.
*Integration tests* should be moved to https://github.com/jbosstools/jbosstools-integration-tests/
See also JBIDE-13796
> JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13411
> URL: https://issues.jboss.org/browse/JBIDE-13411
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, Visual Page Editor Templates
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.1.x
>
> Attachments: tests-vs-tycho-build-time.png
>
>
> On a good day, tests will run and all pass in under 4hrs.
> On a grey day, tests will have failures but complete in under 6hrs.
> On a bad day, tests will stall out and the job will fail when it hits its duration upper limit of 8hrs.
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> Surely some of these tests are:
> a) integration, not unit test, and should be relocated to https://github.com/jbosstools/jbosstools-integration-tests/ and run as part of a new job like https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... ?
> b) reliant on UI which is blocking, and should therefore be rewritten so as to not block test execution?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13411) JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-13411 at 3/29/13 2:09 PM:
----------------------------------------------------------------
another clue: -Dtycho.localArtifacts=ignore speeds up the build twice (w/o tests)
was (Author: dgolovin):
another glue: -Dtycho.localArtifacts=ignore speed up the build twice (w/o tests)
> JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13411
> URL: https://issues.jboss.org/browse/JBIDE-13411
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, Visual Page Editor Templates
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.1.x
>
> Attachments: tests-vs-tycho-build-time.png
>
>
> On a good day, tests will run and all pass in under 4hrs.
> On a grey day, tests will have failures but complete in under 6hrs.
> On a bad day, tests will stall out and the job will fail when it hits its duration upper limit of 8hrs.
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> Surely some of these tests are:
> a) integration, not unit test, and should be relocated to https://github.com/jbosstools/jbosstools-integration-tests/ and run as part of a new job like https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... ?
> b) reliant on UI which is blocking, and should therefore be rewritten so as to not block test execution?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13411) JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-13411:
---------------------------------------
another glue: -Dtycho.localArtifacts=ignore speed up the build twice (w/o tests)
> JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13411
> URL: https://issues.jboss.org/browse/JBIDE-13411
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, Visual Page Editor Templates
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.1.x
>
> Attachments: tests-vs-tycho-build-time.png
>
>
> On a good day, tests will run and all pass in under 4hrs.
> On a grey day, tests will have failures but complete in under 6hrs.
> On a bad day, tests will stall out and the job will fail when it hits its duration upper limit of 8hrs.
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> Surely some of these tests are:
> a) integration, not unit test, and should be relocated to https://github.com/jbosstools/jbosstools-integration-tests/ and run as part of a new job like https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... ?
> b) reliant on UI which is blocking, and should therefore be rewritten so as to not block test execution?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13856) Test jQuery Mobile Palette Wizards on different platforms
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13856?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-13856:
----------------------------------
Description:
If system font size is set to large, wizard should take it into account.
For instance:
!ubuntu_64_large_font_toggle.png!
Windows 8 32bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
jQuery Mobile Palette Widget Wizards work fine.
Windows 8 64bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
Wizards do not start
{code}
org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser])
at org.eclipse.swt.SWT.error(SWT.java:4373)
at org.eclipse.swt.SWT.error(SWT.java:4288)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1057)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:941)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
Caused by: org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]
at org.eclipse.swt.SWT.error(SWT.java:4399)
at org.eclipse.swt.browser.WebKit.create(WebKit.java:542)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
at org.eclipse.jface.window.Window.create(Window.java:431)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95)
at org.eclipse.jface.window.Window.open(Window.java:790)
at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 24 more
{code}
Windows 8 32 and 64 bits (Eclipse+Java) Base+JST + Safari:
jQuery Mobile Palette Widget Wizards work without JavaScript.
Windows 7 32 and 64 bits (Eclipse+Java) Base+JST + Safari:
jQuery Mobile Palette Widget Wizards work without JavaScript.
Windows 7 32 and 64 bit (Eclipse+Java) Base+JST+VPE+Xulrunner:
jQuery Mobile Palette Widget Wizards work fine.
Windows 7 32bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
jQuery Mobile Palette Widget Wizards work fine.
Windows 7 32 and 64 bits (Eclipse+Java) Base+JST:
Wizards do not start
{code}
org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser])
at org.eclipse.swt.SWT.error(SWT.java:4392)
at org.eclipse.swt.SWT.error(SWT.java:4307)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4145)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3762)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
Caused by: org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]
at org.eclipse.swt.SWT.error(SWT.java:4418)
at org.eclipse.swt.browser.WebKit.create(WebKit.java:542)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
at org.eclipse.jface.window.Window.create(Window.java:432)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95)
at org.eclipse.jface.window.Window.open(Window.java:791)
at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 24 more
{code}
MacOs 64 bit (Eclipse+Java) Base+JST+VPE+Xulrunner:
and
MacOs 64 bit (Eclipse+Java) Base+JST:
jQuery Mobile Palette Widget Wizards work fine.
was:
If system font size is set to large, wizard should take it into account.
For instance:
!ubuntu_64_large_font_toggle.png!
Windows 8 32bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
jQuery Mobile Palette Widget Wizards work fine.
Windows 8 64bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
{code}
org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser])
at org.eclipse.swt.SWT.error(SWT.java:4373)
at org.eclipse.swt.SWT.error(SWT.java:4288)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1057)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:941)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
Caused by: org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]
at org.eclipse.swt.SWT.error(SWT.java:4399)
at org.eclipse.swt.browser.WebKit.create(WebKit.java:542)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
at org.eclipse.jface.window.Window.create(Window.java:431)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95)
at org.eclipse.jface.window.Window.open(Window.java:790)
at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 24 more
{code}
Windows 8 32 and 64 bits (Eclipse+Java) Base+JST + Safari:
jQuery Mobile Palette Widget Wizards work without JavaScript.
Windows 7 32 and 64 bits (Eclipse+Java) Base+JST + Safari:
jQuery Mobile Palette Widget Wizards work without JavaScript.
Windows 7 32 and 64 bit (Eclipse+Java) Base+JST+VPE+Xulrunner:
jQuery Mobile Palette Widget Wizards work fine.
Windows 7 32bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
jQuery Mobile Palette Widget Wizards work fine.
Windows 7 32 and 64 bits (Eclipse+Java) Base+JST:
{code}
org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser])
at org.eclipse.swt.SWT.error(SWT.java:4392)
at org.eclipse.swt.SWT.error(SWT.java:4307)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4145)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3762)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
Caused by: org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]
at org.eclipse.swt.SWT.error(SWT.java:4418)
at org.eclipse.swt.browser.WebKit.create(WebKit.java:542)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
at org.eclipse.jface.window.Window.create(Window.java:432)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95)
at org.eclipse.jface.window.Window.open(Window.java:791)
at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 24 more
{code}
MacOs 64 bit (Eclipse+Java) Base+JST+VPE+Xulrunner:
and
MacOs 64 bit (Eclipse+Java) Base+JST:
jQuery Mobile Palette Widget Wizards work fine.
> Test jQuery Mobile Palette Wizards on different platforms
> ---------------------------------------------------------
>
> Key: JBIDE-13856
> URL: https://issues.jboss.org/browse/JBIDE-13856
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jsp/jsf/xml/html source editing
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Alpha2
>
> Attachments: ubuntu_64_button.png, ubuntu_64_checkboxes.png, ubuntu_64_cjeckbox.png, ubuntu_64_collapsible.png, ubuntu_64_dialog.png, ubuntu_64_footerbar.png, ubuntu_64_grid.png, ubuntu_64_headerbar.png, ubuntu_64_large_font_toggle.png, ubuntu_64_link.png, ubuntu_64_listview.png, ubuntu_64_navbar.png, ubuntu_64_page.png, ubuntu_64_radio.png, ubuntu_64_slider.png, ubuntu_64_textinput.png, ubuntu_64_toggle.png
>
>
> If system font size is set to large, wizard should take it into account.
> For instance:
> !ubuntu_64_large_font_toggle.png!
> Windows 8 32bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
> jQuery Mobile Palette Widget Wizards work fine.
> Windows 8 64bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
> Wizards do not start
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser])
> at org.eclipse.swt.SWT.error(SWT.java:4373)
> at org.eclipse.swt.SWT.error(SWT.java:4288)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1057)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:941)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]
> at org.eclipse.swt.SWT.error(SWT.java:4399)
> at org.eclipse.swt.browser.WebKit.create(WebKit.java:542)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
> at org.eclipse.jface.window.Window.create(Window.java:431)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95)
> at org.eclipse.jface.window.Window.open(Window.java:790)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
> at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {code}
> Windows 8 32 and 64 bits (Eclipse+Java) Base+JST + Safari:
> jQuery Mobile Palette Widget Wizards work without JavaScript.
> Windows 7 32 and 64 bits (Eclipse+Java) Base+JST + Safari:
> jQuery Mobile Palette Widget Wizards work without JavaScript.
> Windows 7 32 and 64 bit (Eclipse+Java) Base+JST+VPE+Xulrunner:
> jQuery Mobile Palette Widget Wizards work fine.
> Windows 7 32bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
> jQuery Mobile Palette Widget Wizards work fine.
> Windows 7 32 and 64 bits (Eclipse+Java) Base+JST:
> Wizards do not start
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser])
> at org.eclipse.swt.SWT.error(SWT.java:4392)
> at org.eclipse.swt.SWT.error(SWT.java:4307)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4145)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3762)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]
> at org.eclipse.swt.SWT.error(SWT.java:4418)
> at org.eclipse.swt.browser.WebKit.create(WebKit.java:542)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
> at org.eclipse.jface.window.Window.create(Window.java:432)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95)
> at org.eclipse.jface.window.Window.open(Window.java:791)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
> at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {code}
> MacOs 64 bit (Eclipse+Java) Base+JST+VPE+Xulrunner:
> and
> MacOs 64 bit (Eclipse+Java) Base+JST:
> jQuery Mobile Palette Widget Wizards work fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years