February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13424) BrowserSim: broken layout on Fedora 17. UI elements are shifted down

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13424?page=com.atlassian.jira.plugi... ] Yahor Radtsevich commented on JBIDE-13424: ------------------------------------------ Before this fix if you change default system fonts, they would be changed in BrowserSim too. After this fix default font settings will not affect BrowserSim, because the font size is specified [in the code|https://github.com/jbosstools/jbosstools-vpe/commit/2a77b55cf67a73cf...]. > BrowserSim: broken layout on Fedora 17. UI elements are shifted down > -------------------------------------------------------------------- > > Key: JBIDE-13424 > URL: https://issues.jboss.org/browse/JBIDE-13424 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Affects Versions: 4.0.0.Final > Reporter: Yahor Radtsevich > Assignee: Ilya Buziuk > Fix For: 4.1.0.Alpha1 > > Attachments: screenshot.png > > > See screenshot: > !screenshot.png! -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13424) BrowserSim: broken layout on Fedora 17. UI elements are shifted down

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13424?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-13424: --------------------------------------- What would happen if I change default font size in settings? > BrowserSim: broken layout on Fedora 17. UI elements are shifted down > -------------------------------------------------------------------- > > Key: JBIDE-13424 > URL: https://issues.jboss.org/browse/JBIDE-13424 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Affects Versions: 4.0.0.Final > Reporter: Yahor Radtsevich > Assignee: Ilya Buziuk > Fix For: 4.1.0.Alpha1 > > Attachments: screenshot.png > > > See screenshot: > !screenshot.png! -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13424) BrowserSim: broken layout on Fedora 17. UI elements are shifted down

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13424?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-13424: ------------------------------------- Yep, thats right - this bug was also under ubuntu (just not so noticeable). The root of the issue was tightly coupled with the default font size under linux distros. For instance, default font under fedora was bigger than under ubuntu - layout breakage was more obvious. Now under all Linux distros the font will be pretty the same. > BrowserSim: broken layout on Fedora 17. UI elements are shifted down > -------------------------------------------------------------------- > > Key: JBIDE-13424 > URL: https://issues.jboss.org/browse/JBIDE-13424 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Affects Versions: 4.0.0.Final > Reporter: Yahor Radtsevich > Assignee: Ilya Buziuk > Fix For: 4.1.0.Alpha1 > > Attachments: screenshot.png > > > See screenshot: > !screenshot.png! -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13424) BrowserSim: broken layout on Fedora 17. UI elements are shifted down

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13424?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-13424: ------------------------------------- Fix Version/s: 4.1.0.Alpha1 (was: 4.1.x) > BrowserSim: broken layout on Fedora 17. UI elements are shifted down > -------------------------------------------------------------------- > > Key: JBIDE-13424 > URL: https://issues.jboss.org/browse/JBIDE-13424 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Affects Versions: 4.0.0.Final > Reporter: Yahor Radtsevich > Assignee: Ilya Buziuk > Fix For: 4.1.0.Alpha1 > > Attachments: screenshot.png > > > See screenshot: > !screenshot.png! -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13424) BrowserSim: broken layout on Fedora 17. UI elements are shifted down

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13424?page=com.atlassian.jira.plugi... ] Yahor Radtsevich reassigned JBIDE-13424: ---------------------------------------- Assignee: Ilya Buziuk (was: Yahor Radtsevich) > BrowserSim: broken layout on Fedora 17. UI elements are shifted down > -------------------------------------------------------------------- > > Key: JBIDE-13424 > URL: https://issues.jboss.org/browse/JBIDE-13424 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Affects Versions: 4.0.0.Final > Reporter: Yahor Radtsevich > Assignee: Ilya Buziuk > Fix For: 4.1.x > > Attachments: screenshot.png > > > See screenshot: > !screenshot.png! -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13473) Should provide "Runtime Container" option if none are apecified

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-13473: ------------------------------------- Summary: Should provide "Runtime Container" option if none are apecified Key: JBIDE-13473 URL: https://issues.jboss.org/browse/JBIDE-13473 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: testing Affects Versions: 4.0.0.Final Reporter: Snjezana Peco Assignee: Snjezana Peco Steps new Maven project configure Arquillian create new Arquillian Test Case Run As Arquillian Test case 'Launching MyBeanTestCase has encountered and error. Arquillian tests require at least one container on classpath" If no profiles are active and/or none are defined as default, the plugin should suggest which profiles/containers to run this test with. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13472) Should default or ask for which Arquillian version to use

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-13472: ------------------------------------- Summary: Should default or ask for which Arquillian version to use Key: JBIDE-13472 URL: https://issues.jboss.org/browse/JBIDE-13472 Project: Tools (JBoss Tools) Issue Type: Bug Components: testing Affects Versions: 4.0.0.Final Reporter: Snjezana Peco Assignee: Snjezana Peco Steps new Workspace new Maven Project Configure -> Add Arquillian Support (Ignore the "Arquillian Settings" link in the dialog) Next The generated POM now is invalid. It's missing The Arquillian Version settings should be included in the Setup dialog. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13471) Should not allow to "Create Arquillian Test Case" without having Arquillian setup

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-13471: ------------------------------------- Summary: Should not allow to "Create Arquillian Test Case" without having Arquillian setup Key: JBIDE-13471 URL: https://issues.jboss.org/browse/JBIDE-13471 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: testing Affects Versions: 4.0.0.Final Reporter: Snjezana Peco Assignee: Snjezana Peco Recreate Steps Create a new maven project Right Click -> ** New Arquillian Test Case At this point, you have a non compiling test. The plugin should detect missing Arquillian Artifacts and ask to set it up first. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13470) Missing parent Pom?

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-13470: ------------------------------------- Summary: Missing parent Pom? Key: JBIDE-13470 URL: https://issues.jboss.org/browse/JBIDE-13470 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: testing Affects Versions: 4.0.0.Final Reporter: Snjezana Peco Assignee: Snjezana Peco Importing this as a Maven project doesn't work. Only pom in core is found, and it's complaining bout missing parent pom? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11164) Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11164?page=com.atlassian.jira.plugi... ] Jiri Peterka updated JBIDE-11164: --------------------------------- Fix Version/s: 3.3.x > Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor > ------------------------------------------------------------------------------------- > > Key: JBIDE-11164 > URL: https://issues.jboss.org/browse/JBIDE-11164 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 3.3.0.Beta1 > Environment: jbosstools-3.3_stable_branch.aggregate-Update-2012-02-29_14-32-12-H100.zip,L64 > Reporter: Jiri Peterka > Assignee: Jiri Peterka > Priority: Minor > Fix For: 3.3.0.Beta3, 3.3.x > > > !ENTRY org.eclipse.ui.workbench 4 0 2012-03-05 13:27:01.277 > !MESSAGE Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor > !STACK 0 > java.lang.RuntimeException: Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor > at org.eclipse.ui.internal.WorkbenchPartReference$1.widgetDisposed(WorkbenchPartReference.java:171) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1263) > at org.eclipse.swt.widgets.Widget.release(Widget.java:1080) > at org.eclipse.swt.widgets.Control.release(Control.java:3488) > at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1294) > at org.eclipse.swt.widgets.Widget.release(Widget.java:1083) > at org.eclipse.swt.widgets.Control.release(Control.java:3488) > at org.eclipse.swt.widgets.Widget.dispose(Widget.java:462) > at org.eclipse.ui.internal.EditorSashContainer.disposeParent(EditorSashContainer.java:195) > at org.eclipse.ui.internal.PartSashContainer.dispose(PartSashContainer.java:599) > at org.eclipse.ui.internal.EditorSashContainer.dispose(EditorSashContainer.java:187) > at org.eclipse.ui.internal.EditorAreaHelper.dispose(EditorAreaHelper.java:125) > at org.eclipse.ui.internal.WorkbenchPage.dispose(WorkbenchPage.java:1898) > at org.eclipse.ui.internal.WorkbenchWindow.closeAllPages(WorkbenchWindow.java:894) > at org.eclipse.ui.internal.WorkbenchWindow.hardClose(WorkbenchWindow.java:1729) > at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:730) > at org.eclipse.ui.internal.WorkbenchWindow.access$0(WorkbenchWindow.java:715) > at org.eclipse.ui.internal.WorkbenchWindow$6.run(WorkbenchWindow.java:867) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:865) > at org.eclipse.jface.window.WindowManager.close(WindowManager.java:109) > at org.eclipse.ui.internal.Workbench$18.run(Workbench.java:1114) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1111) > at org.eclipse.ui.internal.Workbench.access$15(Workbench.java:1040) > at org.eclipse.ui.internal.Workbench$25.run(Workbench.java:1284) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.internal.Workbench.close(Workbench.java:1282) > at org.eclipse.ui.internal.Workbench.close(Workbench.java:1254) > at org.eclipse.ui.internal.testing.WorkbenchTestable$2.run(WorkbenchTestable.java:124) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) > at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) > at org.eclipse.swtbot.eclipse.core.UITestApplication.start(UITestApplication.java:54) > 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:344) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > 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:622) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) > at org.eclipse.equinox.launcher.Main.run(Main.java:1410) > at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- 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, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2013