April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-127) Debugging should happen in JSDT editor if the project exist in workspace [EBZ#490626]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-127?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-127: ----------------------------- Sprint: devex #6 April 2016 > Debugging should happen in JSDT editor if the project exist in workspace [EBZ#490626] > ------------------------------------------------------------------------------------- > > Key: ERT-127 > URL: https://issues.jboss.org/browse/ERT-127 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Labels: 3.8_M7, Debug, bzira > Fix For: Neon (4.6) M7 > > > For now all debugging happens via Chromium JavaScript editor via virtual file system. However, if the target project exists in the workspace all debugging should happen in jsdt editor via real file system -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22159) Docker image is empty after selecting it from Image search wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22159?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22159: ----------------------------------- Assignee: Viacheslav Kabanovich > Docker image is empty after selecting it from Image search wizard > ----------------------------------------------------------------- > > Key: JBIDE-22159 > URL: https://issues.jboss.org/browse/JBIDE-22159 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > As discovered in https://github.com/jbosstools/jbosstools-openshift/pull/1106#issuecomment..., provided you have a docker and an OpenShift connection: > - In OpenShift Explorer, select the Deploy Image menu > - select the docker connection > - type a docker image name already pulled in the docker daemon > - delete it and click the search... button > - select the same docker image as previously typed > - once the search wizard closes, the docker Image name field is still empty. > See http://screencast.com/t/iTJX7SjB > As per [~scabanovich]: > {quote} > it is possible that validator does not let empty string to model, so model remains with valid previous value. Then, when you select that same value in the dialog, model is notified, but it already has that value and it does not notify ui because it did not change > {quote} > and his fix proposal: > {quote} > before calling setImageName(newValue) check if it has the same value, then call setImageName(""); and only after this check and adjustment call setImageName(newValue). > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22159) Docker image is empty after selecting it from Image search wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22159?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22159: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > Docker image is empty after selecting it from Image search wizard > ----------------------------------------------------------------- > > Key: JBIDE-22159 > URL: https://issues.jboss.org/browse/JBIDE-22159 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > As discovered in https://github.com/jbosstools/jbosstools-openshift/pull/1106#issuecomment..., provided you have a docker and an OpenShift connection: > - In OpenShift Explorer, select the Deploy Image menu > - select the docker connection > - type a docker image name already pulled in the docker daemon > - delete it and click the search... button > - select the same docker image as previously typed > - once the search wizard closes, the docker Image name field is still empty. > See http://screencast.com/t/iTJX7SjB > As per [~scabanovich]: > {quote} > it is possible that validator does not let empty string to model, so model remains with valid previous value. Then, when you select that same value in the dialog, model is notified, but it already has that value and it does not notify ui because it did not change > {quote} > and his fix proposal: > {quote} > before calling setImageName(newValue) check if it has the same value, then call setImageName(""); and only after this check and adjustment call setImageName(newValue). > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22159) Docker image is empty after selecting it from Image search wizard

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-22159: ----------------------------------- Summary: Docker image is empty after selecting it from Image search wizard Key: JBIDE-22159 URL: https://issues.jboss.org/browse/JBIDE-22159 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Fred Bricon As discovered in https://github.com/jbosstools/jbosstools-openshift/pull/1106#issuecomment..., provided you have a docker and an OpenShift connection: - In OpenShift Explorer, select the Deploy Image menu - select the docker connection - type a docker image name already pulled in the docker daemon - delete it and click the search... button - select the same docker image as previously typed - once the search wizard closes, the docker Image name field is still empty. See http://screencast.com/t/iTJX7SjB As per [~scabanovich]: {quote} it is possible that validator does not let empty string to model, so model remains with valid previous value. Then, when you select that same value in the dialog, model is notified, but it already has that value and it does not notify ui because it did not change {quote} and his fix proposal: {quote} before calling setImageName(newValue) check if it has the same value, then call setImageName(""); and only after this check and adjustment call setImageName(newValue). {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22126) Application wizard: local template buttons are truncated

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22126?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22126: ------------------------------------- Can anyone else reproduce this issue? [~mlabuda], [~mmalina]? [~ldimaggio] do you have a way to test this PR from source? Worst case scenario, we apply [~scabanovich]'s patch and revert it if [~ldimaggio] doesn't see any improvement. > Application wizard: local template buttons are truncated > -------------------------------------------------------- > > Key: JBIDE-22126 > URL: https://issues.jboss.org/browse/JBIDE-22126 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Len DiMaggio > Assignee: Viacheslav Kabanovich > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: local-template-buttons.png, openshift_buttons.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20597) Add connection management to deploy image wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20597?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20597: -------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.4.x) > Add connection management to deploy image wizard > ------------------------------------------------ > > Key: JBIDE-20597 > URL: https://issues.jboss.org/browse/JBIDE-20597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff MAURY > Labels: docker > Fix For: 4.4.0.Alpha1 > > > clicked this nice "Deploy to openshift" menu in Docker and the dialog that shows up is just a lot of fields with no values. > Cannot create a new connection or project. > Makes it hard to get started ;/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22158) bzira needs to support multiple regex matches for Platform, JSDT, WTP, m2e, etc.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22158?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22158: ------------------------------- Description: Currently, bzira supports two ways to define mappings: a) hardcoded list: {code} def map_linuxtools(version): versions = { "4.2.1" : "Mars.2 (4.5)", "4.2.0" : "Mars.2 (4.5)", "4.1.0" : "Mars.1 (4.5)", "4.0.0" : "Mars (4.5)", "5.0.0" : "Neon (4.6)", "---" : NO_VERSION } return versions.get(version, None) {code} b) regex mapping: {code} "Platform" : (lambda version: re.sub(r"4.6(.*)", r"Neon (4.6)\1", version)), {code} But for Platform, we need two sets of mappings for 4.6 (Neon) and 4.7 (Oxygen). Here's a BZ for which we have a target milestone of 4.7: https://bugs.eclipse.org/bugs/show_bug.cgi?id=484347 and here's currently the error that bzira reports: {code} [DEBUG] 484347 - [JFace] MessageDialog should use Link instead of Text [Platform, UI, [4.7]] {20160323T17:24:18} (19 days, 4:16:34.025318) -> https://bugs.eclipse.org/484347 [DEBUG] Mapper: Platform / 4.7 -> 4.7 [ERROR] Version '4.7' mapped from '4.7' not found in ERT. Please create it or fix the mapping. Bug: #484347 NEW - Platform-UI-Inbox(a)eclipse.org - [JFace] MessageDialog should use Link instead of Text Query: https://issues.jboss.org/rest/api/2/search?jql=project+%3D+ERT+and+summar... [INFO] https://bugs.eclipse.org/484347 already proxied as https://issues.jboss.org/browse/ERT-33; checking if something needs updating/syncing. {code} There's an existing issue https://issues.jboss.org/browse/ERT-33 but it has fixversion of "Neon (4.6) M6" despite the fact that the bugzilla now has a target milestone of 4.7 was: Currently, bzira supports two ways to define mappings: a) hardcoded list: {code} def map_linuxtools(version): versions = { "4.2.1" : "Mars.2 (4.5)", "4.2.0" : "Mars.2 (4.5)", "4.1.0" : "Mars.1 (4.5)", "4.0.0" : "Mars (4.5)", "5.0.0" : "Neon (4.6)", "---" : NO_VERSION } return versions.get(version, None) {code} b) regex mapping: {code} "Platform" : (lambda version: re.sub(r"4.6(.*)", r"Neon (4.6)\1", version)), {code} But for Platform, we need two sets of mappings for 4.6 (Neon) and 4.7 (Oxygen). Here's a BZ for which we have a target milestone of 4.7: https://bugs.eclipse.org/bugs/show_bug.cgi?id=484347 and here's currently the error that bzira reports: {code} [DEBUG] 484347 - [JFace] MessageDialog should use Link instead of Text [Platform, UI, [4.7]] {20160323T17:24:18} (19 days, 4:16:34.025318) -> https://bugs.eclipse.org/484347 [DEBUG] Mapper: Platform / 4.7 -> 4.7 [ERROR] Version '4.7' mapped from '4.7' not found in ERT. Please create it or fix the mapping. Bug: #484347 NEW - Platform-UI-Inbox(a)eclipse.org - [JFace] MessageDialog should use Link instead of Text Query: https://issues.jboss.org/rest/api/2/search?jql=project+%3D+ERT+and+summar... [INFO] https://bugs.eclipse.org/484347 already proxied as https://issues.jboss.org/browse/ERT-33; checking if something needs updating/syncing. {code} > bzira needs to support multiple regex matches for Platform, JSDT, WTP, m2e, etc. > -------------------------------------------------------------------------------- > > Key: JBIDE-22158 > URL: https://issues.jboss.org/browse/JBIDE-22158 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > > Currently, bzira supports two ways to define mappings: > a) hardcoded list: > {code} > def map_linuxtools(version): > versions = { > "4.2.1" : "Mars.2 (4.5)", > "4.2.0" : "Mars.2 (4.5)", > "4.1.0" : "Mars.1 (4.5)", > "4.0.0" : "Mars (4.5)", > "5.0.0" : "Neon (4.6)", > "---" : NO_VERSION > } > return versions.get(version, None) > {code} > b) regex mapping: > {code} > "Platform" : (lambda version: re.sub(r"4.6(.*)", r"Neon (4.6)\1", version)), > {code} > But for Platform, we need two sets of mappings for 4.6 (Neon) and 4.7 (Oxygen). > Here's a BZ for which we have a target milestone of 4.7: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=484347 > and here's currently the error that bzira reports: > {code} > [DEBUG] 484347 - [JFace] MessageDialog should use Link instead of Text [Platform, UI, [4.7]] {20160323T17:24:18} (19 days, 4:16:34.025318) -> https://bugs.eclipse.org/484347 > [DEBUG] Mapper: Platform / 4.7 -> 4.7 > [ERROR] Version '4.7' mapped from '4.7' not found in ERT. Please create it or fix the mapping. Bug: #484347 NEW - Platform-UI-Inbox(a)eclipse.org - [JFace] MessageDialog should use Link instead of Text > Query: https://issues.jboss.org/rest/api/2/search?jql=project+%3D+ERT+and+summar... > [INFO] https://bugs.eclipse.org/484347 already proxied as https://issues.jboss.org/browse/ERT-33; checking if something needs updating/syncing. > {code} > There's an existing issue https://issues.jboss.org/browse/ERT-33 but it has fixversion of "Neon (4.6) M6" despite the fact that the bugzilla now has a target milestone of 4.7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22158) bzira needs to support multiple regex matches for Platform, JSDT, WTP, m2e, etc.

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-22158: ---------------------------------- Summary: bzira needs to support multiple regex matches for Platform, JSDT, WTP, m2e, etc. Key: JBIDE-22158 URL: https://issues.jboss.org/browse/JBIDE-22158 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.0.Alpha1 Reporter: Nick Boldt Currently, bzira supports two ways to define mappings: a) hardcoded list: {code} def map_linuxtools(version): versions = { "4.2.1" : "Mars.2 (4.5)", "4.2.0" : "Mars.2 (4.5)", "4.1.0" : "Mars.1 (4.5)", "4.0.0" : "Mars (4.5)", "5.0.0" : "Neon (4.6)", "---" : NO_VERSION } return versions.get(version, None) {code} b) regex mapping: {code} "Platform" : (lambda version: re.sub(r"4.6(.*)", r"Neon (4.6)\1", version)), {code} But for Platform, we need two sets of mappings for 4.6 (Neon) and 4.7 (Oxygen). Here's a BZ for which we have a target milestone of 4.7: https://bugs.eclipse.org/bugs/show_bug.cgi?id=484347 and here's currently the error that bzira reports: {code} [DEBUG] 484347 - [JFace] MessageDialog should use Link instead of Text [Platform, UI, [4.7]] {20160323T17:24:18} (19 days, 4:16:34.025318) -> https://bugs.eclipse.org/484347 [DEBUG] Mapper: Platform / 4.7 -> 4.7 [ERROR] Version '4.7' mapped from '4.7' not found in ERT. Please create it or fix the mapping. Bug: #484347 NEW - Platform-UI-Inbox(a)eclipse.org - [JFace] MessageDialog should use Link instead of Text Query: https://issues.jboss.org/rest/api/2/search?jql=project+%3D+ERT+and+summar... [INFO] https://bugs.eclipse.org/484347 already proxied as https://issues.jboss.org/browse/ERT-33; checking if something needs updating/syncing. {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20577) Allow setting exploded or zipped on per-module basis

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20577?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20577: -------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.x) > Allow setting exploded or zipped on per-module basis > ---------------------------------------------------- > > Key: JBIDE-20577 > URL: https://issues.jboss.org/browse/JBIDE-20577 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > While in the past, we automatically zipped up dependent utility projects, we recently switched to allowing exploded utility projects for appserver versions that suppoort it. Some users have determined this is slower for their usecase, and we should investigate giving users more control over this feature. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-131) Node.js launch should not be available on package.json [EBZ#491455]

by Nick Boldt (JIRA)

Nick Boldt created ERT-131: ------------------------------ Summary: Node.js launch should not be available on package.json [EBZ#491455] Key: ERT-131 URL: https://issues.jboss.org/browse/ERT-131 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt It looks like Node launch on a package.json file should be disabled. Basically, there are 2 cases when Node lauch shoud be enabled: 1) IProject with package.json 2) js file (of the project with package.json) / excluding bower_component & n node_modules -- 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 April 2016