January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-9544) Remember the most-recent choices in the Plugin/Command popup

by Koen Aers (JIRA)

Remember the most-recent choices in the Plugin/Command popup ------------------------------------------------------------ Key: JBIDE-9544 URL: https://issues.jboss.org/browse/JBIDE-9544 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Koen Aers -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9528) Implement a 'Quick Access' Feature for Forge Commands

by Koen Aers (JIRA)

Implement a 'Quick Access' Feature for Forge Commands ----------------------------------------------------- Key: JBIDE-9528 URL: https://issues.jboss.org/browse/JBIDE-9528 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Koen Aers Much like the Eclipse Quick Access Feature, pushing 'Cmd+4' should bring up a popup dialog with all the applicable commands. This involves creating a way for the Forge runtime and the Tools to communicate. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
7
0 / 0

[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, 9 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-9659) Cmd+4/Forge menu requires mouse to use, should be able to use keyboard like for Cmd+3

by Max Rydahl Andersen (JIRA)

Cmd+4/Forge menu requires mouse to use, should be able to use keyboard like for Cmd+3 ------------------------------------------------------------------------------------- Key: JBIDE-9659 URL: https://issues.jboss.org/browse/JBIDE-9659 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Reporter: Max Rydahl Andersen Fix For: 3.3.0.M4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
5
0 / 0

[JBoss JIRA] (JBIDE-10551) Mark as deployable dialog has bold font on OSX

by Max Rydahl Andersen (Created) (JIRA)

Mark as deployable dialog has bold font on OSX ---------------------------------------------- Key: JBIDE-10551 URL: https://issues.jboss.org/browse/JBIDE-10551 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.3.0.Beta1 the warning dialog for mark as deployable looks weird - as if <bold> is used. -- 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, 9 months

5
13
0 / 0

[JBoss JIRA] Created: (JBDS-1361) Need to track branch and revision # of contributed code

by Nick Boldt (JIRA)

Need to track branch and revision # of contributed code ------------------------------------------------------- Key: JBDS-1361 URL: https://jira.jboss.org/browse/JBDS-1361 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: Build Affects Versions: 4.0.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt Curerntly, I track SVN_REVISION when it's available in Hudson, which is generally not available because there is more than one checkout done per build. Unavailable: http://download.jboss.org/jbosstools/builds/staging/jbosstools-teiid-desi... http://download.jboss.org/jbosstools/builds/staging/pi4soa-3.1.x/logs/201... Available: http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2.0.Beta... http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2.0.Beta... 1. Therefore, instead of collecting this value from Hudson, we should perhaps scrape the build log to get the data needed. 2. Also, this information needs to be passed through to JBDS somehow as a new artifact after the build (perhaps attached to the buildResults page?) -- 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

13 years, 9 months

3
25
0 / 0

[JBoss JIRA] (JBDS-1944) JBDS Early Access site should only expose single JBDS 5M5 multi-platform installer

by Nick Boldt (Created) (JIRA)

JBDS Early Access site should only expose single JBDS 5M5 multi-platform installer ---------------------------------------------------------------------------------- Key: JBDS-1944 URL: https://issues.jboss.org/browse/JBDS-1944 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: documentation, installer, updatesite Affects Versions: 5.0.0.M5 Reporter: Nick Boldt Fix For: 5.0.0.M5 JBDS Early Access site should only expose single JBDS 5M5 multi-platform installer -- 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, 9 months

9
16
0 / 0

[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, 9 months

3
2
0 / 0

[JBoss JIRA] (JBIDE-10013) Break OpenShift into its own component

by Rob Stryker (Created) (JIRA)

Break OpenShift into its own component -------------------------------------- Key: JBIDE-10013 URL: https://issues.jboss.org/browse/JBIDE-10013 Project: Tools (JBoss Tools) Issue Type: Task Components: JBossAS/Servers, openshift Affects Versions: 3.3.0.M4 Reporter: Rob Stryker Assignee: Nick Boldt Fix For: 3.3.0.Beta1 Openshift and egit plugins and features and tests need to be moved from the AsTools component into it's own. Steps are as follows: 1) Copy code over 2) Modify descriptors / plugin.xml / feature.xml etc 3) Remove openshift from astools build 4) Add openshift component to beta1 build -- 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, 9 months

6
25
0 / 0

[JBoss JIRA] (JBIDE-10147) Openshift Tools: Extend JBoss Perspective

by Alexey Kazakov (Created) (JIRA)

Openshift Tools: Extend JBoss Perspective ----------------------------------------- Key: JBIDE-10147 URL: https://issues.jboss.org/browse/JBIDE-10147 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Reporter: Alexey Kazakov Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 -- 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, 9 months

7
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2012