November 2013 - jbosstools-issues

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

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9528?page=com.atlassian.jira.plugin... ] Pavol Srna closed JBIDE-9528. ----------------------------- > 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 > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.1.1.Alpha1 > > > 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. 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, 5 months

1
0
0 / 0

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

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9528?page=com.atlassian.jira.plugin... ] Pavol Srna updated JBIDE-9528: ------------------------------ Fix Version/s: (was: 4.2.0.Alpha1) > 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 > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.1.1.Alpha1 > > > 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. 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16118) CLONE - Make sure that Ctrl+4 also works when installed from update site

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16118?page=com.atlassian.jira.plugi... ] Pavol Srna resolved JBIDE-16118. -------------------------------- Resolution: Done > CLONE - Make sure that Ctrl+4 also works when installed from update site > ------------------------------------------------------------------------ > > Key: JBIDE-16118 > URL: https://issues.jboss.org/browse/JBIDE-16118 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.2.0.Alpha1 > > > Currently the Ctrl+4 only works when running as Eclipse runtime. I suspect there must be issues with the module path when launching Forge Runtime when it is installed from the update site. I suspect it does not contain the module with the extra classes allowing for the communication between Forge runtime and Forge tools. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16114) CLONE - Implement a Popup Dialog containing a Table with all the applicable plugin/command combinations

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16114?page=com.atlassian.jira.plugi... ] Pavol Srna resolved JBIDE-16114. -------------------------------- Resolution: Done > CLONE - Implement a Popup Dialog containing a Table with all the applicable plugin/command combinations > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16114 > URL: https://issues.jboss.org/browse/JBIDE-16114 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.2.0.Alpha1 > > > upon selecting the command, this should be pasted into the forge console -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16112) openshift-java-client: remove hard coded default timeout, dont set HttpUrlConnection timeout

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16112?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16112: ------------------------------------- Description: The current code to set timeouts in openshift-java-client is: {code} private int getTimeout(int timeout, int openShiftTimeout, int systemPropertyTimeout, int defaultTimeout) { if (timeout == NO_TIMEOUT) { timeout = openShiftTimeout; if (timeout == NO_TIMEOUT) { timeout = systemPropertyTimeout; if (timeout == NO_TIMEOUT) { timeout = defaultTimeout; } } } return timeout; } {code} calling it looks like this: {code} private void setReadTimeout(int timeout, URLConnection connection) { connection.setReadTimeout( getTimeout( timeout, getSystemPropertyInteger(SYSPROP_OPENSHIFT_READ_TIMEOUT), getSystemPropertyInteger(SYSPROP_DEFAULT_READ_TIMEOUT), DEFAULT_READ_TIMEOUT)); } {code} DEFAULT_READ_TIMEOUT should get eliminated, we should use the SYSPROP_OPENSHIFT_READ_TIMEOUT as this. Furthermore there's no need to set the SYSPROP_DEFAULT_READ_TIMEOUT. > openshift-java-client: remove hard coded default timeout, dont set HttpUrlConnection timeout > -------------------------------------------------------------------------------------------- > > Key: JBIDE-16112 > URL: https://issues.jboss.org/browse/JBIDE-16112 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Fix For: 4.2.x > > > The current code to set timeouts in openshift-java-client is: > {code} > private int getTimeout(int timeout, int openShiftTimeout, int systemPropertyTimeout, int defaultTimeout) { > if (timeout == NO_TIMEOUT) { > timeout = openShiftTimeout; > if (timeout == NO_TIMEOUT) { > timeout = systemPropertyTimeout; > if (timeout == NO_TIMEOUT) { > timeout = defaultTimeout; > } > } > } > return timeout; > } > {code} > calling it looks like this: > {code} > private void setReadTimeout(int timeout, URLConnection connection) { > connection.setReadTimeout( > getTimeout( > timeout, > getSystemPropertyInteger(SYSPROP_OPENSHIFT_READ_TIMEOUT), > getSystemPropertyInteger(SYSPROP_DEFAULT_READ_TIMEOUT), > DEFAULT_READ_TIMEOUT)); > } > {code} > DEFAULT_READ_TIMEOUT should get eliminated, we should use the SYSPROP_OPENSHIFT_READ_TIMEOUT as this. Furthermore there's no need to set the SYSPROP_DEFAULT_READ_TIMEOUT. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16116) CLONE - Add a way of filtering the commands using a text field on top of the Plugin/Command dialog

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16116?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-16116: ------------------------------- Fix Version/s: (was: 4.1.1.Alpha1) > CLONE - Add a way of filtering the commands using a text field on top of the Plugin/Command dialog > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-16116 > URL: https://issues.jboss.org/browse/JBIDE-16116 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.2.0.Alpha1 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16116) CLONE - Add a way of filtering the commands using a text field on top of the Plugin/Command dialog

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16116?page=com.atlassian.jira.plugi... ] Pavol Srna resolved JBIDE-16116. -------------------------------- Resolution: Done > CLONE - Add a way of filtering the commands using a text field on top of the Plugin/Command dialog > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-16116 > URL: https://issues.jboss.org/browse/JBIDE-16116 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.2.0.Alpha1 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16112) openshift-java-client: remove hard coded default timeout, dont set HttpUrlConnection timeout

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16112?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16112: ------------------------------------- Description: The current code to set timeouts in openshift-java-client is: {code} private int getTimeout(int timeout, int openShiftTimeout, int systemPropertyTimeout, int defaultTimeout) { if (timeout == NO_TIMEOUT) { timeout = openShiftTimeout; if (timeout == NO_TIMEOUT) { timeout = systemPropertyTimeout; if (timeout == NO_TIMEOUT) { timeout = defaultTimeout; } } } return timeout; } {code} calling it looks like this: {code} private void setReadTimeout(int timeout, URLConnection connection) { connection.setReadTimeout( getTimeout( timeout, getSystemPropertyInteger(SYSPROP_OPENSHIFT_READ_TIMEOUT), getSystemPropertyInteger(SYSPROP_DEFAULT_READ_TIMEOUT), DEFAULT_READ_TIMEOUT)); } {code} DEFAULT_READ_TIMEOUT should get eliminated, we should use the SYSPROP_OPENSHIFT_READ_TIMEOUT as this. Furthermore there's no need to set the SYSPROP_DEFAULT_READ_TIMEOUT. was: The current code to set timeouts in openshift-java-client is: {code} private int getTimeout(int timeout, int openShiftTimeout, int systemPropertyTimeout, int defaultTimeout) { if (timeout == NO_TIMEOUT) { timeout = openShiftTimeout; if (timeout == NO_TIMEOUT) { timeout = systemPropertyTimeout; if (timeout == NO_TIMEOUT) { timeout = defaultTimeout; } } } return timeout; } {code} calling it looks like this: {code} private void setReadTimeout(int timeout, URLConnection connection) { connection.setReadTimeout( getTimeout( timeout, getSystemPropertyInteger(SYSPROP_OPENSHIFT_READ_TIMEOUT), getSystemPropertyInteger(SYSPROP_DEFAULT_READ_TIMEOUT), DEFAULT_READ_TIMEOUT)); } {code} DEFAULT_READ_TIMEOUT should get eliminated, we should use the SYSPROP_OPENSHIFT_READ_TIMEOUT as this. Furthermore there's no need to set the SYSPROP_DEFAULT_READ_TIMEOUT. > openshift-java-client: remove hard coded default timeout, dont set HttpUrlConnection timeout > -------------------------------------------------------------------------------------------- > > Key: JBIDE-16112 > URL: https://issues.jboss.org/browse/JBIDE-16112 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Fix For: 4.2.x > > > The current code to set timeouts in openshift-java-client is: > {code} > private int getTimeout(int timeout, int openShiftTimeout, int systemPropertyTimeout, int defaultTimeout) { > if (timeout == NO_TIMEOUT) { > timeout = openShiftTimeout; > if (timeout == NO_TIMEOUT) { > timeout = systemPropertyTimeout; > if (timeout == NO_TIMEOUT) { > timeout = defaultTimeout; > } > } > } > return timeout; > } > {code} > calling it looks like this: > {code} > private void setReadTimeout(int timeout, URLConnection connection) { > connection.setReadTimeout( > getTimeout( > timeout, > getSystemPropertyInteger(SYSPROP_OPENSHIFT_READ_TIMEOUT), > getSystemPropertyInteger(SYSPROP_DEFAULT_READ_TIMEOUT), > DEFAULT_READ_TIMEOUT)); > } > {code} > DEFAULT_READ_TIMEOUT should get eliminated, we should use the SYSPROP_OPENSHIFT_READ_TIMEOUT as this. Furthermore there's no need to set the SYSPROP_DEFAULT_READ_TIMEOUT. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16118) CLONE - Make sure that Ctrl+4 also works when installed from update site

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16118?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-16118: ------------------------------- Fix Version/s: (was: 4.1.1.Alpha1) > CLONE - Make sure that Ctrl+4 also works when installed from update site > ------------------------------------------------------------------------ > > Key: JBIDE-16118 > URL: https://issues.jboss.org/browse/JBIDE-16118 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.2.0.Alpha1 > > > Currently the Ctrl+4 only works when running as Eclipse runtime. I suspect there must be issues with the module path when launching Forge Runtime when it is installed from the update site. I suspect it does not contain the module with the extra classes allowing for the communication between Forge runtime and Forge tools. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16114) CLONE - Implement a Popup Dialog containing a Table with all the applicable plugin/command combinations

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16114?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-16114: ------------------------------- Fix Version/s: (was: 4.1.1.Alpha1) > CLONE - Implement a Popup Dialog containing a Table with all the applicable plugin/command combinations > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16114 > URL: https://issues.jboss.org/browse/JBIDE-16114 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.2.0.Alpha1 > > > upon selecting the command, this should be pasted into the forge console -- 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, 5 months

1
0
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 November 2013