April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22227) Hotcode replace fails on local wildfly if breakpoint is set

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22227?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-22227. --------------------------------- Assignee: Rob Stryker Resolution: Done pushed to master > Hotcode replace fails on local wildfly if breakpoint is set > ----------------------------------------------------------- > > Key: JBIDE-22227 > URL: https://issues.jboss.org/browse/JBIDE-22227 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > When debugging a local wildfly server with a deployed servlet, making a breaking change such as method name or signature will fail. > This will pop up a dialog asking to restart the module or the server, which is expected. However, after that, non-breaking changes will still also pop up the hotcode-failed dialog, when it shouldn't. > Workflow: > 1) Create a dynamic web project with simple servlet > 2) Start a wildfly 10 in debug mode and deploy the web project > 3) Run-on-server the servlet object and verify it shows expected output > 4) Set a breakpoint inside the doGet() method > 5) refresh browser (breakpoint gets hit), press play > 6) Make a non-breaking change (change text inside doGet()) > 7) refresh website, verify breakpoint is hit, website content is updated > 8) make a breaking change by adding a new method > 9) hotcode-replace dialog appears. Press 'restart module' > 10) refresh web browser, verify breakpoint is hit, output has changed as expected > 11) make a non-breaking change in output of doGet() > 12) ASSERT: hotcode replace dialog does NOT show - THIS STEP FAILS -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-60) JSON Editor formatter is broken [EBZ#486524]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-60?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-60: ---------------------------- Story Points: 20 > JSON Editor formatter is broken [EBZ#486524] > -------------------------------------------- > > Key: ERT-60 > URL: https://issues.jboss.org/browse/ERT-60 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Max Rydahl Andersen > Labels: bzira, wst.json > > Open a JSON editor and do a source>format. > In my tests a simple JSON such as > { > "test":123 > > } > has been formatted to > { > "test":123 > > } > } > and a more complex example > { > "test":123, > "field2":"f", > "ignore": [ > "examples", > "test", > "tools" > ] > } > ended up as > { > "test":123 > > }"field2":"f" > > }"ignore":["examples","test","tools"] > > } > } -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-60) JSON Editor formatter is broken [EBZ#486524]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-60?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-60: ---------------------------- Sprint: devex #6 April 2016 > JSON Editor formatter is broken [EBZ#486524] > -------------------------------------------- > > Key: ERT-60 > URL: https://issues.jboss.org/browse/ERT-60 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Max Rydahl Andersen > Labels: bzira, wst.json > > Open a JSON editor and do a source>format. > In my tests a simple JSON such as > { > "test":123 > > } > has been formatted to > { > "test":123 > > } > } > and a more complex example > { > "test":123, > "field2":"f", > "ignore": [ > "examples", > "test", > "tools" > ] > } > ended up as > { > "test":123 > > }"field2":"f" > > }"ignore":["examples","test","tools"] > > } > } -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-60) JSON Editor formatter is broken [EBZ#486524]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-60?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan reassigned ERT-60: ------------------------------- Assignee: Snjezana Peco > JSON Editor formatter is broken [EBZ#486524] > -------------------------------------------- > > Key: ERT-60 > URL: https://issues.jboss.org/browse/ERT-60 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Labels: bzira, wst.json > > Open a JSON editor and do a source>format. > In my tests a simple JSON such as > { > "test":123 > > } > has been formatted to > { > "test":123 > > } > } > and a more complex example > { > "test":123, > "field2":"f", > "ignore": [ > "examples", > "test", > "tools" > ] > } > ended up as > { > "test":123 > > }"field2":"f" > > }"ignore":["examples","test","tools"] > > } > } -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-64) Synchronization problems between IJSONModel and the editor. [EBZ#486861]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-64?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan closed ERT-64. --------------------------- Resolution: Duplicate Issue > Synchronization problems between IJSONModel and the editor. [EBZ#486861] > ------------------------------------------------------------------------ > > Key: ERT-64 > URL: https://issues.jboss.org/browse/ERT-64 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Nick Boldt > Labels: bzira, wst.json > > Synchronization of the model is the main problem today with JSON Editor. It causes problem with completion which doesn't work after updating the JSON editor content because the model is not synchronized with the editor (if you close the editor and reopen it, completion works again) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22202) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22202?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22202: ----------------------------------- Component/s: eclipse-migration > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master > ----------------------------------------------------------------------------- > > Key: JBIDE-22202 > URL: https://issues.jboss.org/browse/JBIDE-22202 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, eclipse-migration > Reporter: Rob Stryker > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] > See also: JBDS-3843 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22227) Hotcode replace fails on local wildfly if breakpoint is set

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-22227: ----------------------------------- Summary: Hotcode replace fails on local wildfly if breakpoint is set Key: JBIDE-22227 URL: https://issues.jboss.org/browse/JBIDE-22227 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.4.0.Alpha1 Reporter: Rob Stryker When debugging a local wildfly server with a deployed servlet, making a breaking change such as method name or signature will fail. This will pop up a dialog asking to restart the module or the server, which is expected. However, after that, non-breaking changes will still also pop up the hotcode-failed dialog, when it shouldn't. Workflow: 1) Create a dynamic web project with simple servlet 2) Start a wildfly 10 in debug mode and deploy the web project 3) Run-on-server the servlet object and verify it shows expected output 4) Set a breakpoint inside the doGet() method 5) refresh browser (breakpoint gets hit), press play 6) Make a non-breaking change (change text inside doGet()) 7) refresh website, verify breakpoint is hit, website content is updated 8) make a breaking change by adding a new method 9) hotcode-replace dialog appears. Press 'restart module' 10) refresh web browser, verify breakpoint is hit, output has changed as expected 11) make a non-breaking change in output of doGet() 12) ASSERT: hotcode replace dialog does NOT show - THIS STEP FAILS -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22223) Not appropriate label to start a build from build config

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22223?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22223: ----------------------------------------------- This looks like a duplicate of JBIDE-21885 and first confirmation that the bug does take place. > Not appropriate label to start a build from build config > -------------------------------------------------------- > > Key: JBIDE-22223 > URL: https://issues.jboss.org/browse/JBIDE-22223 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3 > > In context menu of a build configuration in Properties view there was (in 4.3.x) menu item "Start Build" to trigger a new build from build configuration. In nightly build of JBDS a build configuration has item "Start Build ()" what seems to be strange - those parenthesis. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22223) Not appropriate label to start a build from build config

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22223?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22223 at 4/20/16 4:08 PM: ------------------------------------------------------------------------ This looks like a duplicate of JBIDE-21885 and one more confirmation that the bug does take place. was (Author: scabanovich): This looks like a duplicate of JBIDE-21885 and first confirmation that the bug does take place. > Not appropriate label to start a build from build config > -------------------------------------------------------- > > Key: JBIDE-22223 > URL: https://issues.jboss.org/browse/JBIDE-22223 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3 > > In context menu of a build configuration in Properties view there was (in 4.3.x) menu item "Start Build" to trigger a new build from build configuration. In nightly build of JBDS a build configuration has item "Start Build ()" what seems to be strange - those parenthesis. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-17) [EPIC] Support node.js debugging [EBZ#479466]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-17?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-17: ---------------------------- Summary: [EPIC] Support node.js debugging [EBZ#479466] (was: Support node.js debugging [EBZ#479466]) > [EPIC] Support node.js debugging [EBZ#479466] > --------------------------------------------- > > Key: ERT-17 > URL: https://issues.jboss.org/browse/ERT-17 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Priority: Trivial > Labels: 3.8_M5, Debug, bzira > Fix For: Neon (4.6) M5 > > -- 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