March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21863) WatchManager makes multiple callbacks for same event

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21863?page=com.atlassian.jira.plugi... ] Jeff Cantrill resolved JBIDE-21863. ----------------------------------- Resolution: Done > WatchManager makes multiple callbacks for same event > ---------------------------------------------------- > > Key: JBIDE-21863 > URL: https://issues.jboss.org/browse/JBIDE-21863 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > There is an issue in either the WatchClient or the the dependent functionality of the the openshift-rest-client where a new listener is registered when the watch restarts from a timeout. Listeners should only be able registered once -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21449) WatchManager makes multiple callbacks for same event

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21449?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21449: --------------------------------------- [~adietish] Created new PR which removes the barrier, adds listener per kind per project. Looks to have resolved the blocking issue and multiple callback. Please test your scenario when you have an opportunity. > WatchManager makes multiple callbacks for same event > ---------------------------------------------------- > > Key: JBIDE-21449 > URL: https://issues.jboss.org/browse/JBIDE-21449 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.1.CR1 > > > There is an issue in either the WatchClient or the the dependent functionality of the the openshift-rest-client where a new listener is registered when the watch restarts from a timeout. Listeners should only be able registered once -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19933: ------------------------------------ So to generalize this idea to multiple parallel branches, you want to bootstrap a fresh branch by copying the current CI builds (individual projects, aggregates, jobs, etc.) from the tip of the current branch into a new location. Thus... * copy previously built CI output from *master* to *4.4.neon*, then branch for next branch, eg., *4.4.0.Alpha1x*. Or, * copy previously built CI output from *jbosstools-4.3.x* to *4.3.mars*, then branch for next branch, eg., *4.3.1.Beta2x*. Correct? > Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it > --------------------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.x > > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19933: ------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it > --------------------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.x > > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-35) Launch configuration for node.js applications [EBZ#484597]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-35?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-35: ---------------------------- Sprint: devex #4 March 2016 > Launch configuration for node.js applications [EBZ#484597] > ----------------------------------------------------------- > > Key: ERT-35 > URL: https://issues.jboss.org/browse/ERT-35 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: 3.8_M7, Debug, bzira > Fix For: Neon (4.6) M7 > > > We need a launch configuration that can understand package.json file on a project and launch/debug a JS application on a local node.js instance. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-35) Launch configuration for node.js applications [EBZ#484597]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-35?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-35: ---------------------------- Story Points: 5 (was: 25) > Launch configuration for node.js applications [EBZ#484597] > ----------------------------------------------------------- > > Key: ERT-35 > URL: https://issues.jboss.org/browse/ERT-35 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: 3.8_M7, Debug, bzira > Fix For: Neon (4.6) M7 > > > We need a launch configuration that can understand package.json file on a project and launch/debug a JS application on a local node.js instance. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21449) WatchManager makes multiple callbacks for same event

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21449?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-21449: ---------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1023, https://github.com/jbosstools/jbosstools-openshift/pull/1027, https://github.com/openshift/openshift-restclient-java/pull/128 (was: https://github.com/jbosstools/jbosstools-openshift/pull/1023, https://github.com/jbosstools/jbosstools-openshift/pull/1027) > WatchManager makes multiple callbacks for same event > ---------------------------------------------------- > > Key: JBIDE-21449 > URL: https://issues.jboss.org/browse/JBIDE-21449 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.1.CR1 > > > There is an issue in either the WatchClient or the the dependent functionality of the the openshift-rest-client where a new listener is registered when the watch restarts from a timeout. Listeners should only be able registered once -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-78) Improve the information shown while hovering over a variable during a JS debugging session [EBZ#487055]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-78?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-78: ---------------------------- Story Points: 1 > Improve the information shown while hovering over a variable during a JS debugging session [EBZ#487055] > ------------------------------------------------------------------------------------------------------- > > Key: ERT-78 > URL: https://issues.jboss.org/browse/ERT-78 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: 3.8_M6, Debug, bzira > Fix For: Neon (4.6) M6 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-78) Improve the information shown while hovering over a variable during a JS debugging session [EBZ#487055]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-78?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-78: ---------------------------- Sprint: devex #4 March 2016 > Improve the information shown while hovering over a variable during a JS debugging session [EBZ#487055] > ------------------------------------------------------------------------------------------------------- > > Key: ERT-78 > URL: https://issues.jboss.org/browse/ERT-78 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: 3.8_M6, Debug, bzira > Fix For: Neon (4.6) M6 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3620) Account page should take into consideration that login request can be long term operation

by Josephine Qian (JIRA)

[ https://issues.jboss.org/browse/JBDS-3620?page=com.atlassian.jira.plugin.... ] Josephine Qian commented on JBDS-3620: -------------------------------------- Please see the suggestions for timeout message and disabled login button. (I can't add attachment here for some reason) Let me know if you have any questions or comments. [~jowilson][~dgolovin] https://goo.gl/photos/P18pThCvTc4oicnTA Note: 1. Please borrow the spinner and inline notification directly from PatternFly. 2. There is a color change on the disabled button. > Account page should take into consideration that login request can be long term operation > ----------------------------------------------------------------------------------------- > > Key: JBDS-3620 > URL: https://issues.jboss.org/browse/JBDS-3620 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Denis Golovin > Assignee: Joshua Wilson > Priority: Critical > Labels: havoc, ui > Fix For: 9.1.0.CR1 > > > Would be good to: > 1. Show progress animation; > 2. Lock [Log In] button; > 3. Have a timeout for login operation with error show in the end and button unlocked for another attempt. > Currently auth fails in browser with error below > {code}Gateway Timeout > The proxy server did not receive a timely response from the upstream server. > Reference #1.5434d417.1452674127.644f0c55 > {code} > which makes installer to look like being in broken state: > - no errors; > - [Log In] can be pressed many times without any reaction -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 March 2016