December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-3509) Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss

by Marek Goldmann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3509?page=com.atlassian.jira.plugin... ] Marek Goldmann commented on JBIDE-3509: --------------------------------------- It's already done: https://apps.fedoraproject.org/packages/eclipse-jbosstools > Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss > ----------------------------------------------------------------------------------------- > > Key: JBIDE-3509 > URL: https://issues.jboss.org/browse/JBIDE-3509 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Priority: Optional > Fix For: LATER > > > John Ford (John64 on Freenode), a college student from Seneca, has expressed interest in packaging JBT for Fedora. This is a placeholder to track that progress as it relates to the JBT 3.0.0 release, possibly as part of Fedora 11? > Details: http://fedoraproject.org/wiki/JBoss -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3509) Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3509?page=com.atlassian.jira.plugin... ] Mickael Istria commented on JBIDE-3509: --------------------------------------- [~goldmann] Are you aware of plans/progress to rpm-ize JBoss Tools or JBoss Developer Studio? > Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss > ----------------------------------------------------------------------------------------- > > Key: JBIDE-3509 > URL: https://issues.jboss.org/browse/JBIDE-3509 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Priority: Optional > Fix For: LATER > > > John Ford (John64 on Freenode), a college student from Seneca, has expressed interest in packaging JBT for Fedora. This is a placeholder to track that progress as it relates to the JBT 3.0.0 release, possibly as part of Fedora 11? > Details: http://fedoraproject.org/wiki/JBoss -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3509) Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss

by Alexander Kurtakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3509?page=com.atlassian.jira.plugin... ] Alexander Kurtakov commented on JBIDE-3509: ------------------------------------------- Not that I know. You would better ask Marek Goldmann. > Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss > ----------------------------------------------------------------------------------------- > > Key: JBIDE-3509 > URL: https://issues.jboss.org/browse/JBIDE-3509 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Priority: Optional > Fix For: LATER > > > John Ford (John64 on Freenode), a college student from Seneca, has expressed interest in packaging JBT for Fedora. This is a placeholder to track that progress as it relates to the JBT 3.0.0 release, possibly as part of Fedora 11? > Details: http://fedoraproject.org/wiki/JBoss -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13096) SSH key wizard: Add Existing SSH key: automatically provide sensible default-name

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13096?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13096: ------------------------------------- Assignee: (was: Andre Dietisheim) > SSH key wizard: Add Existing SSH key: automatically provide sensible default-name > --------------------------------------------------------------------------------- > > Key: JBIDE-13096 > URL: https://issues.jboss.org/browse/JBIDE-13096 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Beta2 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > > When adding an existing ssh key the user is required to provide a name for the key he's adding (uploading). To the newbie user it is not obvious what he shall provide as name. We should help here a provide some sensible default name. > How to reproduce: > # ASSERT: make sure you have an account on OpenShift and in the OpenShift Explorer > # EXEC: in the OpenShift Explorer: pick "Manage SSH Keys..." from the context-menu of your user > # EXEC: in the upcoming dialog: hit "Add" > Result: > You get a dialog that asks you to browse and select your key and provide a name for it. > Expected: > Automatically provide some meaningful default name so that the newbie user may just pick his key and upload. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13096) SSH key wizard: Add Existing SSH key: automatically provide sensible default-name

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13096?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13096: ------------------------------------- Labels: sshkeys_wizard (was: ) > SSH key wizard: Add Existing SSH key: automatically provide sensible default-name > --------------------------------------------------------------------------------- > > Key: JBIDE-13096 > URL: https://issues.jboss.org/browse/JBIDE-13096 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Beta2 > Reporter: Andre Dietisheim > Priority: Minor > Labels: sshkeys_wizard > Fix For: 4.2.x > > > When adding an existing ssh key the user is required to provide a name for the key he's adding (uploading). To the newbie user it is not obvious what he shall provide as name. We should help here a provide some sensible default name. > How to reproduce: > # ASSERT: make sure you have an account on OpenShift and in the OpenShift Explorer > # EXEC: in the OpenShift Explorer: pick "Manage SSH Keys..." from the context-menu of your user > # EXEC: in the upcoming dialog: hit "Add" > Result: > You get a dialog that asks you to browse and select your key and provide a name for it. > Expected: > Automatically provide some meaningful default name so that the newbie user may just pick his key and upload. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13096) SSH key wizard: Add Existing SSH key: automatically provide sensible default-name

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13096?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13096: ------------------------------------- Estimated Difficulty: Low > SSH key wizard: Add Existing SSH key: automatically provide sensible default-name > --------------------------------------------------------------------------------- > > Key: JBIDE-13096 > URL: https://issues.jboss.org/browse/JBIDE-13096 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.0.0.Beta2 > Reporter: Andre Dietisheim > Priority: Minor > Labels: sshkeys_wizard > Fix For: 4.2.x > > > When adding an existing ssh key the user is required to provide a name for the key he's adding (uploading). To the newbie user it is not obvious what he shall provide as name. We should help here a provide some sensible default name. > How to reproduce: > # ASSERT: make sure you have an account on OpenShift and in the OpenShift Explorer > # EXEC: in the OpenShift Explorer: pick "Manage SSH Keys..." from the context-menu of your user > # EXEC: in the upcoming dialog: hit "Add" > Result: > You get a dialog that asks you to browse and select your key and provide a name for it. > Expected: > Automatically provide some meaningful default name so that the newbie user may just pick his key and upload. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10546) Add ability to import an existing application to OpenShift through the 'Configure' item within the context menu of an application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10546?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10546: ------------------------------------- Assignee: (was: Andre Dietisheim) > Add ability to import an existing application to OpenShift through the 'Configure' item within the context menu of an application > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10546 > URL: https://issues.jboss.org/browse/JBIDE-10546 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.M5 > Reporter: Isaac Rooskov > Fix For: 4.2.0.Alpha2 > > > The 3.3.0.M5 new and noteworthy information highlights the ability to take an application that exists in the workspace and port it to OpenShift; however it has to be done through the OpenShift application creation wizard. > A more intuitive place for this ability to be might be within the context menu of an application in the workspace. The option to 'Import to OpenShift' could sit under the 'Configure' menu item. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10546) Add ability to import an existing application to OpenShift through the 'Configure' item within the context menu of an application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10546?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10546: ------------------------------------- Estimated Difficulty: Low > Add ability to import an existing application to OpenShift through the 'Configure' item within the context menu of an application > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10546 > URL: https://issues.jboss.org/browse/JBIDE-10546 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.M5 > Reporter: Isaac Rooskov > Fix For: 4.2.0.Alpha2 > > > The 3.3.0.M5 new and noteworthy information highlights the ability to take an application that exists in the workspace and port it to OpenShift; however it has to be done through the OpenShift application creation wizard. > A more intuitive place for this ability to be might be within the context menu of an application in the workspace. The option to 'Import to OpenShift' could sit under the 'Configure' menu item. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12851) Server Adapter wizard: link should point to creation wizard in case user don't have app/domain

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12851?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12851: ------------------------------------- Estimated Difficulty: Low > Server Adapter wizard: link should point to creation wizard in case user don't have app/domain > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-12851 > URL: https://issues.jboss.org/browse/JBIDE-12851 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.0.0.Beta1 > Reporter: Stefan Bunciak > Priority: Minor > Labels: server_adapter_wizard > Fix For: 4.2.x > > Attachments: newappserver.png > > > In case the user doesn't have an application on openshift (or domain) link should point to Create OpenShift Application wizard not to the Import OpenShift Application wizard. Also the link could be named more appropriately in this case - user will be creating application, not importing. > !newappserver.png|thumbnail! -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16108) Preferences: Timeout preferences should not set system properties but operation specific timeout

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16108?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16108: ------------------------------------- Estimated Difficulty: Medium > Preferences: Timeout preferences should not set system properties but operation specific timeout > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-16108 > URL: https://issues.jboss.org/browse/JBIDE-16108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Labels: preferences > Fix For: 4.2.x > > > In JBIDE-16046 we introduced an Eclipse Preferences to set the openshift-java-clilent timeouts. These preferences currently set the lib specific system property which is not good. Consider the following usecase: > 1) User launches Eclipse and has system property set to 10000 (-D): Eclipse Preferences display 10000 > 2) User sets preference to 1234 > 3) restarts Ecllipse: Preferences display 1234 > 3) happens because we load the value from eclipse preferences and override the system property > We should keep both separate: System property and Eclipse preferences: > We use operation specific timeouts in all Eclipse code and make the Eclipse preferences provide some value for this. Leaving the system property alone. > We should also: > * add a checkbox for "[ ] use default" > * change openshift-java-client to differentiate "no value" (<0) and value set (>=0) > * remove current hard-coded safe default in openshift-java-client, replace it by system-property we already have). -- 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, 3 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 December 2013