[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
[JBoss JIRA] (JBIDE-11064) RSE server startup does not work with AS 7.0.2
by Martin Malina (JIRA)
Martin Malina created JBIDE-11064:
-------------------------------------
Summary: RSE server startup does not work with AS 7.0.2
Key: JBIDE-11064
URL: https://issues.jboss.org/browse/JBIDE-11064
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta1
Environment: jbdevstudio-product-universal-5.0.0.v201202250031M-H77-Beta1.jar
JBoss AS 7.0.2
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.0.Beta1
AS 7.0.2 fails to start using RSE.
!ENTRY org.jboss.ide.eclipse.as.core 4 0 2012-02-27 11:26:24.651
!MESSAGE Error connecting to this server's JMX service: jboss-as-7.0.2.Final on marvin
!STACK 0
java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException
I'm not sure how exactly it works, but I am told that remote JNDI didn't really work in 7.0.2 so maybe that's why?
--
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