[JBoss JIRA] Created: (JBIDE-8090) Missing dialog titles
by Libor Zoubek (JIRA)
Missing dialog titles
---------------------
Key: JBIDE-8090
URL: https://issues.jboss.org/browse/JBIDE-8090
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: deltacloud
Affects Versions: 3.2.0.CR1
Reporter: Libor Zoubek
Assignee: Andre Dietisheim
Priority: Minor
I ve found several dialogs where are missing dialog titles. It should be fixed. It is good convention to have titled dialogs and it is goot for bot tests too.
* New/Edit Connection
* Launch Instance
* Setting up filters
* Selecting EC2 key
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-8730) JBoss Tools Runtime Detection doesn't work
by Vlado Pakan (JIRA)
JBoss Tools Runtime Detection doesn't work
------------------------------------------
Key: JBIDE-8730
URL: https://issues.jboss.org/browse/JBIDE-8730
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtimes
Affects Versions: 3.2.1
Environment: Linux, 3.2_stable_branch.2011-04-15_00-38-24-H707, Java Sun JDK 1.6._24
Reporter: Vlado Pakan
Assignee: Snjezana Peco
Open Window > Preferences > JBoss Tools > JBoss Tools Runtime Detection
Choose button Add and select directory which contains at least one JBoss Runtime
Searching for Runtimes dialog is displayed but doesn't contain any runtime.
Buttons OK and Cancel are enabled but doesn't do anything. Dialog has to be closed using window closing button "X".
After Searching dialog is closed no new path for searching is added to JBoss Tools Runtime Detection table on Preferences dialog.
After reopening of Preferences Dialog new path is displayed in JBoss Tools Runtime Detection table on Preferences dialog.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
by Denis Golovin (JIRA)
VPE Part should not show exceptions but readable explanation why it cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://jira.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.M2
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Maxim Areshkau
Fix For: 3.2.0.Beta2
Exceptions related to loading xulrunner should be handled right way. Human friendly messages would be good here for usecases we know. VPE should check for current platform and if it is not supported do not scary users with exceptions. It should try to load XL just in case path to XL injected outside through System property, but show explanation instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported platforms and possible workarounds. please read this article on JBoss Tools Community Portal". If someone is trying to inject XULRunner implementation using system property it can say, That "Visual Editor tried to load XL from provided loaction ${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-8831) org.jboss.tools.vpe.test suite failes with NPE ?
by Nick Boldt (JIRA)
org.jboss.tools.vpe.test suite failes with NPE ?
------------------------------------------------
Key: JBIDE-8831
URL: https://issues.jboss.org/browse/JBIDE-8831
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: testing, Visual Page Editor core
Affects Versions: 3.2.1.M1
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Fix For: 3.2.1.M1
No idea what's causing this test failure.
http://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/job/jbosst...
[INFO] org.jboss.tools.vpe.test .......................... FAILURE [46.855s]
[ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-test-plugin:0.10.0:test (default-test) on project org.jboss.tools.vpe.test: There are test failures.
[ERROR] Please refer to /mnt/hudson_workspace/workspace/jbosstools-3.2_stable_branch.tests/sources/vpe/tests/org.jboss.tools.vpe.test/target/surefire-reports for the individual test results.
http://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/job/jbosst...
Test set: org.jboss.tools.vpe.test.VpeAllTests
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.47 sec
http://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/job/jbosst...
!ENTRY org.eclipse.osgi 4 0 2011-05-02 05:52:14.441
!MESSAGE Application error
!STACK 1
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:4083)
at org.eclipse.swt.SWT.error(SWT.java:3998)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164)
at org.eclipse.swt.widgets.Display.release(Display.java:3215)
at org.eclipse.swt.graphics.Device.dispose(Device.java:246)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:131)
at org.codehaus.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:21)
at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:109)
at org.codehaus.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:27)
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:369)
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:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
Caused by: java.lang.NullPointerException
at org.eclipse.ui.internal.menus.WorkbenchMenuService.handleRegistryChanges(WorkbenchMenuService.java:1084)
at org.eclipse.ui.internal.menus.WorkbenchMenuService$2.run(WorkbenchMenuService.java:274)
at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:164)
at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:158)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
... 21 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months