July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22747) Several context menu items in context menu of an OpenShift 2 server adapter do not work

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22747?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22747: ------------------------------------- Fix Version/s: 4.4.1.AM3 > Several context menu items in context menu of an OpenShift 2 server adapter do not work > --------------------------------------------------------------------------------------- > > Key: JBIDE-22747 > URL: https://issues.jboss.org/browse/JBIDE-22747 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v2 > Fix For: 4.4.1.AM3 > > > When I click on some context menu items on OpenShift 2 Server adapter, nothing happens. It works when opened via context menu of an application in OpenShift explorer view. > Following context menu items are not working: > - OpenShift - Port Forwarding... > - OpenShift - Tail Files... > - OpenShift - Snapshot - Save... > - OpenShift - Snapshot - Restore/Deploy... > - OpenShift - Details... > - OpenShift - Edit Embedded Cartridges... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22694) Environment Var Wizard: Improve deletion of environment variables

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22694?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22694: ------------------------------------- Fix Version/s: 4.4.1.AM3 > Environment Var Wizard: Improve deletion of environment variables > ----------------------------------------------------------------- > > Key: JBIDE-22694 > URL: https://issues.jboss.org/browse/JBIDE-22694 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Marián Labuda > Labels: env_var_wizard, openshift_v3 > Fix For: 4.4.1.AM3 > > > Deletion of environment variable does not match user expectation. If I delete an environment variable which has been added in earlier opened and closed Env. Var wizard, this variable has prefix [deleted]. I don't think this is good practice, we should be consistent across all wizards and dialog, so once user select an env var in table and push Delete button, value should be removed from the table. No labelling should be done here, the table should reflect real current state of environment variable (what it is gonna look like once I hit Finish button). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22694) Environment Var Wizard: Improve deletion of environment variables

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22694?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22694 at 7/26/16 6:16 PM: ------------------------------------------------------------------- I believe that the 2 usecases where the user hits "Delete" by mistaken can be easily handled with a customary "Are you sure?" dialog. It can can get annoying though if we dont offer deletion of multiple entries. But to me the dialog is more "usual"/"familiar" than the [deleted] prefix. I agree that directly deleting entries would then in consequence mean that we would have to reinsert (deleted) entries in the table and they would somehow "magically" reappear. Here too we could improve the situation by informing the user about the changes that will be applied when he hits "Reset" (and ask him to confirm). I believe that this matches git since both apply changes directly and only show differences upon request. There also is another behaviour that feels inconsistent to me. We only have the [deleted] prefix for variables that are loaded from the server. If you add a variable and, a few seconds later delete it (without exiting the wizard), the variable disappears instantly. It wont get prefixed. Deleting directly seems far more familiar to me, but I might still miss something? was (Author: adietish): I believe that the 2 usecases where the user hits "Delete" by mistaken can be easily handled with a customary "Are you sure?" dialog. It can can get annoying though if we dont offer deletion of multiple entries. But to me the dialog is more "usual"/"familiar" than the [deleted] prefix. I agree that directly deleting entries would then in consequence mean that we would have to reinsert (deleted) entries in the table and they would somehow "magically" reappear. Here too we could improve the situation by informing the user about the changes that will be applied when he hits "Reset" (and ask him to confirm). I believe that this matches git since both apply changes directly and only show differences upon request. Deleting directly seems far more familiar to me, but I might still miss something? > Environment Var Wizard: Improve deletion of environment variables > ----------------------------------------------------------------- > > Key: JBIDE-22694 > URL: https://issues.jboss.org/browse/JBIDE-22694 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Marián Labuda > Labels: env_var_wizard, openshift_v3 > > Deletion of environment variable does not match user expectation. If I delete an environment variable which has been added in earlier opened and closed Env. Var wizard, this variable has prefix [deleted]. I don't think this is good practice, we should be consistent across all wizards and dialog, so once user select an env var in table and push Delete button, value should be removed from the table. No labelling should be done here, the table should reflect real current state of environment variable (what it is gonna look like once I hit Finish button). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22694) Environment Var Wizard: Improve deletion of environment variables

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22694?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22694: ------------------------------------------ I believe that the 2 usecases where the user hits "Delete" by mistaken can be easily handled with a customary "Are you sure?" dialog. It can can get annoying though if we dont offer deletion of multiple entries. But to me the dialog is more "usual"/"familiar" than the [deleted] prefix. I agree that directly deleting entries would then in consequence mean that we would have to reinsert (deleted) entries in the table and they would somehow "magically" reappear. Here too we could improve the situation by informing the user about the changes that will be applied when he hits "Reset" (and ask him to confirm). I believe that this matches git since both apply changes directly and only show differences upon request. Deleting directly seems far more familiar to me, but I might still miss something? > Environment Var Wizard: Improve deletion of environment variables > ----------------------------------------------------------------- > > Key: JBIDE-22694 > URL: https://issues.jboss.org/browse/JBIDE-22694 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Marián Labuda > Labels: env_var_wizard, openshift_v3 > > Deletion of environment variable does not match user expectation. If I delete an environment variable which has been added in earlier opened and closed Env. Var wizard, this variable has prefix [deleted]. I don't think this is good practice, we should be consistent across all wizards and dialog, so once user select an env var in table and push Delete button, value should be removed from the table. No labelling should be done here, the table should reflect real current state of environment variable (what it is gonna look like once I hit Finish button). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22743) SSH keys are not fetched by default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22743?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22743: ------------------------------------------ [~mlabuda] [~fbricon] [~jeffmaury] what fixVersion are we using for v2 issues given the priority on v3? 4.4.x? > SSH keys are not fetched by default > ----------------------------------- > > Key: JBIDE-22743 > URL: https://issues.jboss.org/browse/JBIDE-22743 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: openshift_v2, sshkeys_wizard > Fix For: LATER > > > In Manage SSH Keys wizard for OpenShift 2 plugin there is a table containing SSH keys uploaded for an OpenShift 2 account. Earlier, if I had uploaded SSH keys elsewhere and then opened Manage SSH Keys shell, those uploaded SSH keys were there by default. Now I have to push Refresh button to get SSH keys. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22743) SSH keys are not fetched by default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22743?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22743: ------------------------------------- Comment: was deleted (was: [~mlabuda] [~fbricon] [~jeffmaury] what fixVersion are we using for v2 issues given the priority on v3? 4.4.x?) > SSH keys are not fetched by default > ----------------------------------- > > Key: JBIDE-22743 > URL: https://issues.jboss.org/browse/JBIDE-22743 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: openshift_v2, sshkeys_wizard > Fix For: LATER > > > In Manage SSH Keys wizard for OpenShift 2 plugin there is a table containing SSH keys uploaded for an OpenShift 2 account. Earlier, if I had uploaded SSH keys elsewhere and then opened Manage SSH Keys shell, those uploaded SSH keys were there by default. Now I have to push Refresh button to get SSH keys. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22743) SSH keys are not fetched by default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22743?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22743: ------------------------------------- Fix Version/s: LATER > SSH keys are not fetched by default > ----------------------------------- > > Key: JBIDE-22743 > URL: https://issues.jboss.org/browse/JBIDE-22743 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: openshift_v2, sshkeys_wizard > Fix For: LATER > > > In Manage SSH Keys wizard for OpenShift 2 plugin there is a table containing SSH keys uploaded for an OpenShift 2 account. Earlier, if I had uploaded SSH keys elsewhere and then opened Manage SSH Keys shell, those uploaded SSH keys were there by default. Now I have to push Refresh button to get SSH keys. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-356) JavaScript Debugger should support mapping between original and minified js files [EBZ#498518]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-356?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-356: ------------------------------- Assignee: Ilya Buziuk > JavaScript Debugger should support mapping between original and minified js files [EBZ#498518] > ---------------------------------------------------------------------------------------------- > > Key: ERT-356 > URL: https://issues.jboss.org/browse/ERT-356 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: Debug, bzira > Fix For: Future > > > minified js files should be mapped to original js files located in the workspace for JavaScript WIP debugging -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-356) JavaScript Debugger should support mapping between original and minified js files [EBZ#498518]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-356?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-356: ---------------------------- Fix Version/s: Future > JavaScript Debugger should support mapping between original and minified js files [EBZ#498518] > ---------------------------------------------------------------------------------------------- > > Key: ERT-356 > URL: https://issues.jboss.org/browse/ERT-356 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: Debug, bzira > Fix For: Future > > > minified js files should be mapped to original js files located in the workspace for JavaScript WIP debugging -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-357) Need to move hot swap on save to functionality from node to chromium plugin [EBZ#498520]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-357?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-357: ---------------------------- Fix Version/s: Neon.1 (4.6) > Need to move hot swap on save to functionality from node to chromium plugin [EBZ#498520] > ---------------------------------------------------------------------------------------- > > Key: ERT-357 > URL: https://issues.jboss.org/browse/ERT-357 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: Debug, bzira > Fix For: Neon.1 (4.6) > > > For now "hot swap on save" code is located in *.jsdt.js.node bundle - Bug 488344. Need to move it to chromium.core so that debugger part could be consumed by adopters with "hot swap on save" functionality available OOTB -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 July 2016