[JBoss JIRA] (JBIDE-16944) Dont show android sdk location error dialog box when users can't/need to fix it
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-16944:
-------------------------------------------
Summary: Dont show android sdk location error dialog box when users can't/need to fix it
Key: JBIDE-16944
URL: https://issues.jboss.org/browse/JBIDE-16944
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Reporter: Max Rydahl Andersen
Priority: Critical
Fix For: 4.2.0.Beta2
using the hybrid wizard the first time breaks the UI guidelines of not showing errors first as it pops up a dialog stating "Android Location not defined".
That is just not a pleasant nor expected workflow, especially if what I'm doing is trying to just do an ios app.
What would be expected is that if the user need to do something before this wizard to run is that it would provide a warning/info on a UI element stating "No XYZ found. Use <link to preferences> to configure a XYZ" or similar.
There are other places this error dialog pops up which we should guard against since it is as a new user something that throws you off guard. Lets be gentle.
--
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
12 years
[JBoss JIRA] (JBIDE-16617) New Hybrid Mobile dialog shows error before anything is entered
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16617?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen resolved JBIDE-16617.
-----------------------------------------
Fix Version/s: 4.2.0.Beta1
(was: 4.2.0.Beta2)
Resolution: Done
after trying some more I can see this specific issue (show no errors on first start) is actually fixed.
The issue about android location I would consider a separate one which i'll create.
> New Hybrid Mobile dialog shows error before anything is entered
> ---------------------------------------------------------------
>
> Key: JBIDE-16617
> URL: https://issues.jboss.org/browse/JBIDE-16617
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Alpha2
> Environment: JBDS 8.0.0.Alpha2b B71
> Reporter: Martin Malina
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.2.0.Beta1
>
> Attachments: hybrid-dialog-1.png, hybrid-dialog-2.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> When you create a new hybrid mobile project (File -> New -> Hybrid Mobile...), on the first page of the dialog, you're shown an error at the top even though you haven't done anything yet.
> This is ugly and violates http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#Wizards Guideline 5.3.
> !hybrid-dialog-1.png!
> Also, consider polishing the next page, too.
> !hybrid-dialog-2.png!
> If I don't have an engine installed, I get the error Please select a Hybrid Mobile Engine. This is not very nice, but I'm not sure how to improve it - perhaps if there are no engines installed, have a different message? And if you have at least one engine, select the first one by default, so that we avoid unnecessary errors?
--
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
12 years
[JBoss JIRA] (JBIDE-16617) New Hybrid Mobile dialog shows error before anything is entered
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16617?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16617:
----------------------------------------
Fix Version/s: 4.2.0.Beta2
(was: 4.2.0.Beta1)
Priority: Critical (was: Major)
This is not blocking beta1 (unless [~gercan] think he can fix this before friday).
But I'm raising the priority on this issue since using this wizard the first time not only breaks the UI guidelines of not showing errors first, but it also pops up a dialog stating "Android Location not defined".
That is just not a pleasant nor expected workflow, especially if what I'm doing is trying to just do an ios app.
What would be expected is that if the user need to do something before this wizard to run is that it would provide a warning/info on a UI element stating "No XYZ found. Use <link to preferences> to configure a XYZ" or similar.
> New Hybrid Mobile dialog shows error before anything is entered
> ---------------------------------------------------------------
>
> Key: JBIDE-16617
> URL: https://issues.jboss.org/browse/JBIDE-16617
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Alpha2
> Environment: JBDS 8.0.0.Alpha2b B71
> Reporter: Martin Malina
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.2.0.Beta2
>
> Attachments: hybrid-dialog-1.png, hybrid-dialog-2.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> When you create a new hybrid mobile project (File -> New -> Hybrid Mobile...), on the first page of the dialog, you're shown an error at the top even though you haven't done anything yet.
> This is ugly and violates http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#Wizards Guideline 5.3.
> !hybrid-dialog-1.png!
> Also, consider polishing the next page, too.
> !hybrid-dialog-2.png!
> If I don't have an engine installed, I get the error Please select a Hybrid Mobile Engine. This is not very nice, but I'm not sure how to improve it - perhaps if there are no engines installed, have a different message? And if you have at least one engine, select the first one by default, so that we avoid unnecessary errors?
--
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
12 years
[JBoss JIRA] (TOOLSDOC-451) Update explicit Kepler text and figs references in docs for 8.0 (Luna)
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-451?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-451:
-------------------------------------
Assignee: Suz Dorfield (was: Michelle Murray)
> Update explicit Kepler text and figs references in docs for 8.0 (Luna)
> ----------------------------------------------------------------------
>
> Key: TOOLSDOC-451
> URL: https://issues.jboss.org/browse/TOOLSDOC-451
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide, Installation Guide, Migration Guide, User Guide
> Reporter: Michelle Murray
> Assignee: Suz Dorfield
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 4 hours
> Time Spent: 35 minutes
> Remaining Estimate: 3 hours, 25 minutes
>
> _Text_
> *Installation Guide*
> * 2.2 Supported Operating Systems and Architectures
> * 3.3 Install JBoss Developer Studio BYOE
> * 5.2 Upgrade from JBoss Developer Studio 6.x and Earlier
> * 5.3 Upgrade from JBoss Developer Studio 7.0
> * 6.3 Uninstall JBoss Developer Studio BYOE
> *Getting Started Guide*
> --
> *Migration Guide*
> * 2.2 Upgrade from JBoss Developer Studio 6.x and Earlier (shared with Install)
> * 2.3 Upgrade from JBoss Developer Studio 7.0 (shared with Install)* 3.1 Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE
> *User Guide*
> --
> _Figs_
> *Installation Guide*
> * Fig 3.6 Ininstall JBoss Developer Studio BYOE via Eclipse Marketplace
> * Fig 3.7 Confirm Selected Features Window
> * Fig 6.2 Uninstall JBoss Developer Studio via Eclipse Marketplace
> * Fig 6.3 Confirm Selected Features Window
> *Getting Started Guide*
> --
> *Migration Guide*
> --
> *User Guide*
> --
--
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
12 years
[JBoss JIRA] (TOOLSDOC-449) Update explicit 7.1 text and figs references in docs for 8.0
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-449?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-449:
-------------------------------------
Assignee: Suz Dorfield (was: Michelle Murray)
> Update explicit 7.1 text and figs references in docs for 8.0
> ------------------------------------------------------------
>
> Key: TOOLSDOC-449
> URL: https://issues.jboss.org/browse/TOOLSDOC-449
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Getting Started Guide, Installation Guide, Migration Guide, User Guide
> Reporter: Michelle Murray
> Assignee: Suz Dorfield
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 1 day, 30 minutes
> Time Spent: 40 minutes
> Remaining Estimate: 7 hours, 50 minutes
>
> _Text_
> *Installation Guide*
> 2.2 Supported Operating Systems and Architectures
> 2.3 Computer Memory
> 2.4 Compatible Java Developer Kits
> 3.2 Install JBoss Developer Studio
> 3.3 Install JBoss Developer Studio BYOE
> 5.2 Upgrade from JBoss Developer Studio 6.x and Earlier
> 5.3 Upgrade from JBoss Developer Studio 7.0
> B.1 Build the Universal Installer from Source
> *Getting Started Guide*
> 2.1 About Getting Started
> 3.1 Installation Assumptions
> 3.2 Install JBoss Developer Studio (shared with Install)
> 4.3 Tutorial Assumptions
> *Migration Guide*
> 2.2 Upgrade from JBoss Developer Studio 6.x and Earlier (shared with Install)
> 2.3 Upgrade from JBoss Developer Studio 7.0 (shared with Install)
> 3.1 Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE
> *User Guide*
> --
> _Figures_
> *Installation Guide*
> 3.2 Installation Step 3: Select Target Folder
> 3.3 Installation Step 4: Select Java VM
> 3.5 Installation Step 7: Installation Progress in Finished State
> 3.6 Install JBoss Developer Studio BYOE via Eclipse Marketplace
> 3.7 Confirm Selected Features Window
> 3.10 Work from an Online Website
> 3.11 Work from a Local Copy of the Update .zip file
> 3.12 Availalble Software Window Listing JBoss Developer Studio 7.x - Bring Your Own Eclipse
> *Getting Started Guide*
> 3.2 Installation Step 3: Select Target Folder (shared with Install)
> 3.3 Installation Step 4: Select Java VM (shared with Install)
> 3.4 Installation Step 7: Installation Progress in Finished State (shared with Install)
> *Migration Guide*
> --
> *User Guide*
> 2.4 JBoss Buzz
> 2.22 Work from a Local Copy of the JBoss Central .zip File
--
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
12 years
[JBoss JIRA] (JBDS-2921) Dropping a file to Editor pane from Nautilus file browser doesn't work
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2921?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2921:
---------------------------------------
[~snjeza], [~fbricon]: As this was a customer reported issue it needs Release Notes text. Please complete the Release Notes Text field. I've completed the first question for you (what was the issue) but need text on how the issue was fixed.
> Dropping a file to Editor pane from Nautilus file browser doesn't work
> ----------------------------------------------------------------------
>
> Key: JBDS-2921
> URL: https://issues.jboss.org/browse/JBDS-2921
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.GA
> Environment: Red Hat Enterprise Linux 6 (Gnome 2)
> Fedora 20 (Gnome 3)
> Reporter: Takayuki Konishi
> Assignee: Snjezana Peco
>
> Dropping a file to Editor pane from Nautilus file browser doesn't work. It works on JBDS 7.0, Eclipse 4.3.0 and Eclipse 4.3.1.
> I got this exception:
> {code:title=$WORKSPACE/.metadata/.log}
> !ENTRY org.eclipse.ui 4 0 2014-02-19 10:56:37.879
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: assertion failed: )
> at org.eclipse.swt.SWT.error(SWT.java:4397)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:622)
> 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.core.runtime.AssertionFailedException: assertion failed:
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.asyncDrop(EditorAreaDropAdapter.java:131)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.access$0(EditorAreaDropAdapter.java:87)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter$1.run(EditorAreaDropAdapter.java:81)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {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
12 years
[JBoss JIRA] (JBDS-2921) Dropping a file to Editor pane from Nautilus file browser doesn't work
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2921?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-2921:
----------------------------------
Release Notes Docs Status: Documented as Resolved Issue
Release Notes Text:
*Replace this text*
Write 2-3 sentences in plain language making sure you answer every question:
# What actions or circumstances caused the problem? How did the problem affect the example/tool/IDE? = On Linux-based operating systems using GNOME desktop, dragging a file from Nautilus File Manager into an Editor view did not open the file.
# What was done to fix the problem?
# What now happens to the example/tool/IDE when the same actions/circumstances occur?
> Dropping a file to Editor pane from Nautilus file browser doesn't work
> ----------------------------------------------------------------------
>
> Key: JBDS-2921
> URL: https://issues.jboss.org/browse/JBDS-2921
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.GA
> Environment: Red Hat Enterprise Linux 6 (Gnome 2)
> Fedora 20 (Gnome 3)
> Reporter: Takayuki Konishi
> Assignee: Snjezana Peco
>
> Dropping a file to Editor pane from Nautilus file browser doesn't work. It works on JBDS 7.0, Eclipse 4.3.0 and Eclipse 4.3.1.
> I got this exception:
> {code:title=$WORKSPACE/.metadata/.log}
> !ENTRY org.eclipse.ui 4 0 2014-02-19 10:56:37.879
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: assertion failed: )
> at org.eclipse.swt.SWT.error(SWT.java:4397)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:622)
> 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.core.runtime.AssertionFailedException: assertion failed:
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.asyncDrop(EditorAreaDropAdapter.java:131)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.access$0(EditorAreaDropAdapter.java:87)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter$1.run(EditorAreaDropAdapter.java:81)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {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
12 years
[JBoss JIRA] (JBDS-2921) Dropping a file to Editor pane from Nautilus file browser doesn't work
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2921?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-2921:
----------------------------------
Release Notes Text:
*Replace this text*
Write 2-3 sentences in plain language making sure you answer every question:
# What actions or circumstances caused the problem? How did the problem affect the example/tool/IDE?
_On Linux-based operating systems using GNOME desktop, dragging a file from Nautilus File Manager into an Editor view did not open the file._
# What was done to fix the problem?
# What now happens to the example/tool/IDE when the same actions/circumstances occur?
was:
*Replace this text*
Write 2-3 sentences in plain language making sure you answer every question:
# What actions or circumstances caused the problem? How did the problem affect the example/tool/IDE? = On Linux-based operating systems using GNOME desktop, dragging a file from Nautilus File Manager into an Editor view did not open the file.
# What was done to fix the problem?
# What now happens to the example/tool/IDE when the same actions/circumstances occur?
> Dropping a file to Editor pane from Nautilus file browser doesn't work
> ----------------------------------------------------------------------
>
> Key: JBDS-2921
> URL: https://issues.jboss.org/browse/JBDS-2921
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.GA
> Environment: Red Hat Enterprise Linux 6 (Gnome 2)
> Fedora 20 (Gnome 3)
> Reporter: Takayuki Konishi
> Assignee: Snjezana Peco
>
> Dropping a file to Editor pane from Nautilus file browser doesn't work. It works on JBDS 7.0, Eclipse 4.3.0 and Eclipse 4.3.1.
> I got this exception:
> {code:title=$WORKSPACE/.metadata/.log}
> !ENTRY org.eclipse.ui 4 0 2014-02-19 10:56:37.879
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: assertion failed: )
> at org.eclipse.swt.SWT.error(SWT.java:4397)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:622)
> 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.core.runtime.AssertionFailedException: assertion failed:
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.asyncDrop(EditorAreaDropAdapter.java:131)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.access$0(EditorAreaDropAdapter.java:87)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter$1.run(EditorAreaDropAdapter.java:81)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {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
12 years
[JBoss JIRA] (JBDS-2921) Dropping a file to Editor pane from Nautilus file browser doesn't work
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2921?page=com.atlassian.jira.plugin.... ]
Michelle Murray resolved JBDS-2921.
-----------------------------------
Resolution: Done
> Dropping a file to Editor pane from Nautilus file browser doesn't work
> ----------------------------------------------------------------------
>
> Key: JBDS-2921
> URL: https://issues.jboss.org/browse/JBDS-2921
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.GA
> Environment: Red Hat Enterprise Linux 6 (Gnome 2)
> Fedora 20 (Gnome 3)
> Reporter: Takayuki Konishi
> Assignee: Snjezana Peco
>
> Dropping a file to Editor pane from Nautilus file browser doesn't work. It works on JBDS 7.0, Eclipse 4.3.0 and Eclipse 4.3.1.
> I got this exception:
> {code:title=$WORKSPACE/.metadata/.log}
> !ENTRY org.eclipse.ui 4 0 2014-02-19 10:56:37.879
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: assertion failed: )
> at org.eclipse.swt.SWT.error(SWT.java:4397)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:622)
> 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.core.runtime.AssertionFailedException: assertion failed:
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.asyncDrop(EditorAreaDropAdapter.java:131)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.access$0(EditorAreaDropAdapter.java:87)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter$1.run(EditorAreaDropAdapter.java:81)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {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
12 years