April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22259) Debugging of OS 3 application creates a new replication controller

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22259?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22259: ---------------------------------- Priority: Critical (was: Major) > Debugging of OS 3 application creates a new replication controller > ------------------------------------------------------------------ > > Key: JBIDE-22259 > URL: https://issues.jboss.org/browse/JBIDE-22259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > > Restart in debug on OS 3 server adapter of eap 6.4 application and related workspace project creates a new replication controller. Every time server is stopped and started, new replication controller is created (although server has been stopped and then started) and a this new replication controller is still debugging (has set debug port). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22259) Debugging of OS 3 application creates a new replication controller

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22259?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22259: ---------------------------------- Labels: openshift_v3 server_adapter (was: ) > Debugging of OS 3 application creates a new replication controller > ------------------------------------------------------------------ > > Key: JBIDE-22259 > URL: https://issues.jboss.org/browse/JBIDE-22259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > > Restart in debug on OS 3 server adapter of eap 6.4 application and related workspace project creates a new replication controller. Every time server is stopped and started, new replication controller is created (although server has been stopped and then started) and a this new replication controller is still debugging (has set debug port). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22259) Debugging of OS 3 application creates a new replication controller

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22259: ------------------------------------- Summary: Debugging of OS 3 application creates a new replication controller Key: JBIDE-22259 URL: https://issues.jboss.org/browse/JBIDE-22259 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Marián Labuda Restart in debug on OS 3 server adapter of eap 6.4 application and related workspace project creates a new replication controller. Every time server is stopped and started, new replication controller is created (although server has been stopped and then started) and a this new replication controller is still debugging (has set debug port). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16647) Allow to fully update application from central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16647?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-16647. ------------------------------- Assignee: Mickael Istria Resolution: Done Reopened/closed to include in current sprint, to account for the time spent analyzing this requirement. > Allow to fully update application from central > ---------------------------------------------- > > Key: JBIDE-16647 > URL: https://issues.jboss.org/browse/JBIDE-16647 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central-update > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.4.x > > > Software/Update tab should contain a more explicit way to update the whole application (same as "Check for Updates" menu). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22229) Tooling to check if patches/PRs are applied across both master and maintenance

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22229?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22229: ------------------------------------ PR merged. Next, steps 2 & 3. > Tooling to check if patches/PRs are applied across both master and maintenance > ------------------------------------------------------------------------------ > > Key: JBIDE-22229 > URL: https://issues.jboss.org/browse/JBIDE-22229 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > 1. review and push https://github.com/jbosstools/jbosstools-build-ci/pull/143 > 2. migrate scripts in jbdevstudio-ci that also use python to generate JIRAs to the same repo > 3. externalize shared JIRA component mapping table so both scripts can use it -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16647) Allow to fully update application from central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16647?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16647: -------------------------------- Story Points: 1 (was: 5) Sprint: devex #113 April 2016 > Allow to fully update application from central > ---------------------------------------------- > > Key: JBIDE-16647 > URL: https://issues.jboss.org/browse/JBIDE-16647 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central-update > Reporter: Mickael Istria > Priority: Minor > Fix For: 4.4.x > > > Software/Update tab should contain a more explicit way to update the whole application (same as "Check for Updates" menu). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16647) Allow to fully update application from central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16647?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-16647. ---------------------------------- Resolution: Rejected I now disagree with myself 2 years ago. Let's reject this jira. > Allow to fully update application from central > ---------------------------------------------- > > Key: JBIDE-16647 > URL: https://issues.jboss.org/browse/JBIDE-16647 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central-update > Reporter: Mickael Istria > Priority: Minor > Fix For: 4.4.x > > > Software/Update tab should contain a more explicit way to update the whole application (same as "Check for Updates" menu). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22255) Number of alterated OpenShift 3 Server Adapter should start from 2 not 1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22255?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22255: ------------------------------------- I agree with Marian though, it should start with 2. We obviously have several implementations of the same thing. I personally wrote https://github.com/jbosstools/jbosstools-server/blob/master/wtp/plugins/o... > Number of alterated OpenShift 3 Server Adapter should start from 2 not 1 > ------------------------------------------------------------------------ > > Key: JBIDE-22255 > URL: https://issues.jboss.org/browse/JBIDE-22255 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3, ux > Fix For: 4.4.x > > > When I create a New OpenShift 3 Server Adapter with same details as already an existing one server adapter, new one has altered label in Server view by number in parentheses. This starts with number 1. > Example: > I am having an OS 3 Server Adapter with label "eap-app at OpenShift 3 (10.1.2.2)" then I create a new OS 3 Server Adapter with same details and I get "eap-app at OpenShift 3 (10.1.2.2) (1)", what I think is not correct, because it is already second. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21007) Do not display OpenShift v2/v3 but rather OpenShift 2/3

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21007?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21007. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5240. > Do not display OpenShift v2/v3 but rather OpenShift 2/3 > ------------------------------------------------------- > > Key: JBIDE-21007 > URL: https://issues.jboss.org/browse/JBIDE-21007 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > [~sspeiche] mentioned today we should not display OpenShift v2/v3 but rather OpenShift 2/3. Need to change all strings in jbosstools-openshift codebase and the JBoss Central connectors (cc [~nickboldt]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21951) Start port forwarding button is disabled after starting and stopping it

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21951?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21951. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5240. > Start port forwarding button is disabled after starting and stopping it > ----------------------------------------------------------------------- > > Key: JBIDE-21951 > URL: https://issues.jboss.org/browse/JBIDE-21951 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.4.0.Alpha1 > > Attachments: video.ogg-2.ogv > > > In Port Forwarding wizard when I start port forwarding, then stop it, the button Start All is disabled and it is not possible to start port forwarding again. Well, both buttons after starting and stopping are disabled, only OK is enabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016