[JBoss JIRA] (JBIDE-10807) GWT invalid Menu Extension
by Rastislav Wagner (JIRA)
Rastislav Wagner created JBIDE-10807:
----------------------------------------
Summary: GWT invalid Menu Extension
Key: JBIDE-10807
URL: https://issues.jboss.org/browse/JBIDE-10807
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: GWT
Affects Versions: 3.3.0.Beta1
Reporter: Rastislav Wagner
Assignee: Andre Dietisheim
Calling context menu of any project throws:
1. Plug-in 'com.google.gwt.eclipse.core' contributed an invalid Menu Extension (Path: 'com.google.gdt.eclipse.suite.popupMenu.project' is invalid): com.google.gwt.eclipse.core.popupMenu.project.gwtSettings
2. Plug-in 'com.google.gwt.eclipse.core' contributed an invalid Menu Extension (Path: 'com.google.gdt.eclipse.suite.popupMenu.project' is invalid): com.google.gwt.eclipse.core.actions.GWTCompileProjectAction
3.Plug-in 'com.google.gwt.eclipse.core' contributed an invalid Menu Extension (Path: 'com.google.gdt.eclipse.suite.popupMenu.project' is invalid): com.google.gwt.eclipse.core.actions.SpeedTracerToolbarAction
An exception stack trace is not available.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (JBIDE-9660) Cmd+4/Forge menu should be possible to activate without having the forge shell active
by Max Rydahl Andersen (JIRA)
Cmd+4/Forge menu should be possible to activate without having the forge shell active
-------------------------------------------------------------------------------------
Key: JBIDE-9660
URL: https://issues.jboss.org/browse/JBIDE-9660
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Reporter: Max Rydahl Andersen
Fix For: 3.3.0.M4
if the forge shell only is possible to show when the forge shell is in focus then its just a fancy ctrl+space thing.
Should be able to call it from outside of the forge UI so it becomes easily accessible.
Challenge is though to ensure forge is in the right directory - but taking the current selection as the directory to ensure forge is operating in should be enough.
Maybe the shell command should show the path for current selection so possible to know what context it will be executed in ?
Possibly even provide a "breadcrumb" style ui allowing users to click on a path segment to choose at what level it will operate.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months