November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21122) Port Forwarding: Start All button should be disabled if port forwarding is already active

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21122?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21122: ------------------------------------- Fix Version/s: 4.3.1.Beta1 > Port Forwarding: Start All button should be disabled if port forwarding is already active > ----------------------------------------------------------------------------------------- > > Key: JBIDE-21122 > URL: https://issues.jboss.org/browse/JBIDE-21122 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.3.1.Beta1 > > > In Port Forwarding wizard is a button "Start All" which starts port forwarding for all services listed in a table. If user triggers the button and port forwarding is already active, Start All is still enabled and user can click on it again and again but nothing happens. Accessibility of this button should be similar as Stop All, which works as expected - if port forwarding is not active, it is disabled, otherwise it is enabled. > There is also a checkbox to find free ports for port forwarding. Once port forwarding is active, checking and unchecking this checkbox do nothing. It should have same accessibility as Start All button - if there is active port forwarding, the checkbox should be disabled, otherwise it should be enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21123) Port forwarding: Free ports for port forwarding are cached even though dialog was canceled

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21123?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21123: ------------------------------------- Summary: Port forwarding: Free ports for port forwarding are cached even though dialog was canceled (was: Free ports for port forwarding are cached even though dialog was canceled) > Port forwarding: Free ports for port forwarding are cached even though dialog was canceled > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21123 > URL: https://issues.jboss.org/browse/JBIDE-21123 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: openshift_v3, port_forwarding_wizard > > In Port forwarding dialog there is a checkbox to use free ports for port forwading. Upon checking this checkbox, free port are used in a table showing services. If user check the checkbox, free ports are used but then cancel the dialog either by pressing Esc or close the dialog, the state of checkbox is cached. If then user opens a dialog again checkbox is not checked but dialog is behaving like it is, because there are used free ports for port forwading. It forces user to check checkbox again, it finds another free ports and then uncheck it to get to default state. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21122) Port Forwarding: Start All button should be disabled if port forwarding is already active

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21122?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21122: ------------------------------------- Summary: Port Forwarding: Start All button should be disabled if port forwarding is already active (was: Start All button should be disabled if port forwarding is already active) > Port Forwarding: Start All button should be disabled if port forwarding is already active > ----------------------------------------------------------------------------------------- > > Key: JBIDE-21122 > URL: https://issues.jboss.org/browse/JBIDE-21122 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > > In Port Forwarding wizard is a button "Start All" which starts port forwarding for all services listed in a table. If user triggers the button and port forwarding is already active, Start All is still enabled and user can click on it again and again but nothing happens. Accessibility of this button should be similar as Stop All, which works as expected - if port forwarding is not active, it is disabled, otherwise it is enabled. > There is also a checkbox to find free ports for port forwarding. Once port forwarding is active, checking and unchecking this checkbox do nothing. It should have same accessibility as Start All button - if there is active port forwarding, the checkbox should be disabled, otherwise it should be enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16128) Publish component sites to Nexus

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16128: ---------------------------------------- Conclusion on that is that it would require workflow change for a more rigourous version management. But so far, the "legacy" versioning and publish mechanism has been working fine and isn't too hard to maintain. So there is no plan to change that for now. However, the ideas and solutions listed in this Jira are valuable if we really want to enfore Nexus usage one day. I'm unassigning and untargeting the issue. > Publish component sites to Nexus > -------------------------------- > > Key: JBIDE-16128 > URL: https://issues.jboss.org/browse/JBIDE-16128 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Priority: Optional > Fix For: LATER > > Attachments: deployWithJenkins.png > > > In order to get a first idea of how easy/difficult it would be to rely on Nexus for publication,we could simply start by configuring CI jobs to also run a "mvn deploy" to deploy the output p2 repository onto Nexus. > Then we'll see what are the pros/cons of this approach. > Current publication process and locations will be kept. These p2 repo on Nexus won't be consumed by aggregator, at least not until we are sure it's worth it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16128) Publish component sites to Nexus

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-16128: ----------------------------------- Fix Version/s: LATER (was: 4.3.x) > Publish component sites to Nexus > -------------------------------- > > Key: JBIDE-16128 > URL: https://issues.jboss.org/browse/JBIDE-16128 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Optional > Fix For: LATER > > Attachments: deployWithJenkins.png > > > In order to get a first idea of how easy/difficult it would be to rely on Nexus for publication,we could simply start by configuring CI jobs to also run a "mvn deploy" to deploy the output p2 repository onto Nexus. > Then we'll see what are the pros/cons of this approach. > Current publication process and locations will be kept. These p2 repo on Nexus won't be consumed by aggregator, at least not until we are sure it's worth it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16128) Publish component sites to Nexus

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-16128: -------------------------------------- Assignee: (was: Mickael Istria) > Publish component sites to Nexus > -------------------------------- > > Key: JBIDE-16128 > URL: https://issues.jboss.org/browse/JBIDE-16128 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Priority: Optional > Fix For: LATER > > Attachments: deployWithJenkins.png > > > In order to get a first idea of how easy/difficult it would be to rely on Nexus for publication,we could simply start by configuring CI jobs to also run a "mvn deploy" to deploy the output p2 repository onto Nexus. > Then we'll see what are the pros/cons of this approach. > Current publication process and locations will be kept. These p2 repo on Nexus won't be consumed by aggregator, at least not until we are sure it's worth it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21121) Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21121?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21121: ------------------------------------- Labels: openshift_v3 (was: ) > Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21121 > URL: https://issues.jboss.org/browse/JBIDE-21121 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.4.0.Alpha1 > > > OpenShift 3 port forwarding features requires 'oc' binary to be set up in tooling. It's done in Workbench preference dialog on page OpenShift 3. If there is no 'oc' binary set and user invokes a port forwarding dialog, it is opened and even Start All button is enabled. User finds out that it is not possible to perform only when he gets an error message upon clicking on Start All button describing the problem. There could be some warning/error dialog popped up before opening a port forwarding dialog if there is no 'oc' location set in preferences. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21121) Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21121?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21121: ------------------------------------- Labels: openshift_v3 port_forwarding_wizard (was: openshift_v3) > Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21121 > URL: https://issues.jboss.org/browse/JBIDE-21121 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.4.0.Alpha1 > > > OpenShift 3 port forwarding features requires 'oc' binary to be set up in tooling. It's done in Workbench preference dialog on page OpenShift 3. If there is no 'oc' binary set and user invokes a port forwarding dialog, it is opened and even Start All button is enabled. User finds out that it is not possible to perform only when he gets an error message upon clicking on Start All button describing the problem. There could be some warning/error dialog popped up before opening a port forwarding dialog if there is no 'oc' location set in preferences. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21121) Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21121?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21121: ------------------------------------- Summary: Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog (was: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog) > Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21121 > URL: https://issues.jboss.org/browse/JBIDE-21121 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > OpenShift 3 port forwarding features requires 'oc' binary to be set up in tooling. It's done in Workbench preference dialog on page OpenShift 3. If there is no 'oc' binary set and user invokes a port forwarding dialog, it is opened and even Start All button is enabled. User finds out that it is not possible to perform only when he gets an error message upon clicking on Start All button describing the problem. There could be some warning/error dialog popped up before opening a port forwarding dialog if there is no 'oc' location set in preferences. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21121) Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21121?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21121: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 > Port Forwarding: Warning/error dialog should pop up if there is no oc binary when opening Port forwarding dialog > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21121 > URL: https://issues.jboss.org/browse/JBIDE-21121 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > OpenShift 3 port forwarding features requires 'oc' binary to be set up in tooling. It's done in Workbench preference dialog on page OpenShift 3. If there is no 'oc' binary set and user invokes a port forwarding dialog, it is opened and even Start All button is enabled. User finds out that it is not possible to perform only when he gets an error message upon clicking on Start All button describing the problem. There could be some warning/error dialog popped up before opening a port forwarding dialog if there is no 'oc' location set in preferences. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 2015