[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, 11 months
[JBoss JIRA] (JBIDE-10055) Remove openshift plugins, tests, sources, features from ~/trunk/as/
by Nick Boldt (Created) (JIRA)
Remove openshift plugins, tests, sources, features from ~/trunk/as/
-------------------------------------------------------------------
Key: JBIDE-10055
URL: https://issues.jboss.org/browse/JBIDE-10055
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Rob Stryker
Fix For: 3.3.0.Beta1
Remove openshift plugins, tests, sources, features from ~/trunk/as/
Remove all TODO markers in pom.xml, site.xml, etc. pertaining to removing stuff that's now in ~/trunk/openshift/
--
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, 11 months
[JBoss JIRA] Created: (JBDS-1839) JAX-RS maven integration plugin is missing in extra site
by Libor Zoubek (JIRA)
JAX-RS maven integration plugin is missing in extra site
--------------------------------------------------------
Key: JBDS-1839
URL: https://issues.jboss.org/browse/JBDS-1839
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: 3rdPartyCertification, maven
Affects Versions: 5.0.0.M3
Reporter: Libor Zoubek
Fix For: 5.0.0.M4
I was verifying JBIDE-9290 on JBDS with m2e. JAX-RS configurator is missing there. It will definitely make sence to include this plugin when jax-rs tooling becomes part of JBDS. But it might make sense to include it before.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months