January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3308) Promote JBoss Tools CAT in JBT/JBDS About box

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3308?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3308: --------------------------------- Project: Developer Studio (JBoss Developer Studio) (was: Tools (JBoss Tools)) Key: JBDS-3308 (was: JBIDE-18872) Workflow: CDW v1 (was: GIT Pull Request workflow ) Affects Version/s: (was: 4.2.0.Final) Component/s: (was: qa) Fix Version/s: (was: 4.2.3.Final) Docs QE Status: NEW > Promote JBoss Tools CAT in JBT/JBDS About box > --------------------------------------------- > > Key: JBDS-3308 > URL: https://issues.jboss.org/browse/JBDS-3308 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Reporter: Vlado Pakan > > Would be nice to put link to JBT CAT or JBT CAT logo with link to it to JBDS/JBT About box to make JBT CAT more visible. > New link/image should be visible without resizing About box -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16951) Update code that uses the OSJC ssh sessions to use the new ApplicationSSHSession class

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16951?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16951: ------------------------------------- Fix Version/s: LATER (was: 4.3.x) > Update code that uses the OSJC ssh sessions to use the new ApplicationSSHSession class > -------------------------------------------------------------------------------------- > > Key: JBIDE-16951 > URL: https://issues.jboss.org/browse/JBIDE-16951 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Corey Daley > Fix For: LATER > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Need to update any code that referenced methods inside of IApplication that used an SSH session to use the new IApplicationSSHSession interface that only contains methods that use the ssh sessions. JIRA for the OSJC can be found here: https://issues.jboss.org/browse/OSJC-54 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17191) Server adapter: allow users to "Debug" OpenShift applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17191?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17191: ------------------------------------- Fix Version/s: LATER (was: 4.3.x) > Server adapter: allow users to "Debug" OpenShift applications > ------------------------------------------------------------- > > Key: JBIDE-17191 > URL: https://issues.jboss.org/browse/JBIDE-17191 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Andre Dietisheim > Labels: server_adapter > Fix For: LATER > > Attachments: cf_eclipse_application_details_debug_start1.png, cf_eclipse_editor_connect_to_debugger.png, debug-server-adapter.png > > Original Estimate: 3 days > Remaining Estimate: 3 days > > traditional server adapters have "Debug", > !debug-server-adapter.png! > We should have this for OpenShift server adapters, too. We also need some launch config for these. > We need to be able to only port forward single ports (not just all like now) in the openshift-java-client. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17191) Server adapter: allow users to "Debug" OpenShift applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17191?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-17191: ------------------------------------------ setting fixVersion to LATER since the main focus now is to create tooling for OpenShift v3. > Server adapter: allow users to "Debug" OpenShift applications > ------------------------------------------------------------- > > Key: JBIDE-17191 > URL: https://issues.jboss.org/browse/JBIDE-17191 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Andre Dietisheim > Labels: server_adapter > Fix For: LATER > > Attachments: cf_eclipse_application_details_debug_start1.png, cf_eclipse_editor_connect_to_debugger.png, debug-server-adapter.png > > Original Estimate: 3 days > Remaining Estimate: 3 days > > traditional server adapters have "Debug", > !debug-server-adapter.png! > We should have this for OpenShift server adapters, too. We also need some launch config for these. > We need to be able to only port forward single ports (not just all like now) in the openshift-java-client. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18082) Application wizard, Connection wizard: Last used connection from explorer is not preselected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18082?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18082: ------------------------------------- Fix Version/s: LATER (was: 4.3.x) > Application wizard, Connection wizard: Last used connection from explorer is not preselected > -------------------------------------------------------------------------------------------- > > Key: JBIDE-18082 > URL: https://issues.jboss.org/browse/JBIDE-18082 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard, connection_wizard > Fix For: LATER > > > In JBIDE-17568 was implemented preselection of last used connection via menu File - New - OpenShift Application. But preselection of last used connection from OpenShift explorer is not working (probably has not been implemented yet). > We should provide preselection also for last used connection via OpenShift explorer. Preselection via Menu now works like this: > User has lets say 2 connections. If he opens New Application wizard via menu File - New - OpenShift Application, then first connection is preselected. He chooses second connection in opened New Application wizard (on the first page containing credentials), clicks Next button and then user clicks Cancel. Then user open New application wizard via menu File - New - OpenShift application again and second connection is preselected. > Suggested solution for explorer: > User has 2 connections and first one is used for preselection. User selects in OpenShift explorer second connection and opens New application wizard via context menu. After closing New application wizard shell (by its completion or canceling) user should get preselected second connection after opening a New Application wizard via menu File - New - OpenShift Application. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18082) Application wizard, Connection wizard: Last used connection from explorer is not preselected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18082?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-18082: ------------------------------------------ setting fixVersion to LATER since the main focus now is to create tooling for OpenShift v3. > Application wizard, Connection wizard: Last used connection from explorer is not preselected > -------------------------------------------------------------------------------------------- > > Key: JBIDE-18082 > URL: https://issues.jboss.org/browse/JBIDE-18082 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard, connection_wizard > Fix For: LATER > > > In JBIDE-17568 was implemented preselection of last used connection via menu File - New - OpenShift Application. But preselection of last used connection from OpenShift explorer is not working (probably has not been implemented yet). > We should provide preselection also for last used connection via OpenShift explorer. Preselection via Menu now works like this: > User has lets say 2 connections. If he opens New Application wizard via menu File - New - OpenShift Application, then first connection is preselected. He chooses second connection in opened New Application wizard (on the first page containing credentials), clicks Next button and then user clicks Cancel. Then user open New application wizard via menu File - New - OpenShift application again and second connection is preselected. > Suggested solution for explorer: > User has 2 connections and first one is used for preselection. User selects in OpenShift explorer second connection and opens New application wizard via context menu. After closing New application wizard shell (by its completion or canceling) user should get preselected second connection after opening a New Application wizard via menu File - New - OpenShift Application. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16371) Application wizard: provide checkboxes for (per application-type) applicable markers

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16371?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16371: ------------------------------------- Fix Version/s: LATER (was: 4.3.x) > Application wizard: provide checkboxes for (per application-type) applicable markers > ------------------------------------------------------------------------------------ > > Key: JBIDE-16371 > URL: https://issues.jboss.org/browse/JBIDE-16371 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.1.Final > Reporter: Andre Dietisheim > Labels: application_wizard > Fix For: LATER > > Attachments: project-page.png > > > Markers in OpenShift allow users to enable/disable functionalities: see JBIDE-14845 > We should offer these markers as toggles in the Application wizard on the project configuration page: > !project-page.png! > In a mail with Max and Burr: > {quote} > for EAP/wildfly/tomcat enable_jpda, disable build and maybe the java7 toggle etc. would be interesting and for other app types other markers could make sense? > {quote} > When implementing this we should consider that most markers, which are not sourcecode related, are by now considered as deprected in OpenShift. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16371) Application wizard: provide checkboxes for (per application-type) applicable markers

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16371?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16371: ------------------------------------------ setting fixVersion to LATER since the main focus now is to create tooling for OpenShift v3. > Application wizard: provide checkboxes for (per application-type) applicable markers > ------------------------------------------------------------------------------------ > > Key: JBIDE-16371 > URL: https://issues.jboss.org/browse/JBIDE-16371 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.1.Final > Reporter: Andre Dietisheim > Labels: application_wizard > Fix For: LATER > > Attachments: project-page.png > > > Markers in OpenShift allow users to enable/disable functionalities: see JBIDE-14845 > We should offer these markers as toggles in the Application wizard on the project configuration page: > !project-page.png! > In a mail with Max and Burr: > {quote} > for EAP/wildfly/tomcat enable_jpda, disable build and maybe the java7 toggle etc. would be interesting and for other app types other markers could make sense? > {quote} > When implementing this we should consider that most markers, which are not sourcecode related, are by now considered as deprected in OpenShift. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18124) Server adapter: Creating a new server adapter does not use name that was provided

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18124?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18124: ------------------------------------- Fix Version/s: LATER (was: 4.3.x) > Server adapter: Creating a new server adapter does not use name that was provided > --------------------------------------------------------------------------------- > > Key: JBIDE-18124 > URL: https://issues.jboss.org/browse/JBIDE-18124 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Fix For: LATER > > > While creating a new server adapter there is a field in New Server shell for Server's host name and Server name. At least the field Server name should be taken into consideration while creating a server adapter and created server adapter should have be named "filledName at OpenShift [Started]" instead of "applicationName at OpenShift [Started]". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18124) Server adapter: Creating a new server adapter does not use name that was provided

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18124?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-18124: ------------------------------------------ setting fixVersion to LATER since the main focus now is to create tooling for OpenShift v3. > Server adapter: Creating a new server adapter does not use name that was provided > --------------------------------------------------------------------------------- > > Key: JBIDE-18124 > URL: https://issues.jboss.org/browse/JBIDE-18124 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Fix For: LATER > > > While creating a new server adapter there is a field in New Server shell for Server's host name and Server name. At least the field Server name should be taken into consideration while creating a server adapter and created server adapter should have be named "filledName at OpenShift [Started]" instead of "applicationName at OpenShift [Started]". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 January 2015