February 2016 - jbosstools-issues

[JBoss JIRA] (ERT-16) Add "Exec" command on a container, using Eclipse Terminal [EBZ#479336]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-16?page=com.atlassian.jira.plugin.sys... ] Nick Boldt updated ERT-16: -------------------------- Labels: 5.0.0 Docker bzira (was: 4.1.0 Docker bzira) > Add "Exec" command on a container, using Eclipse Terminal [EBZ#479336] > ---------------------------------------------------------------------- > > Key: ERT-16 > URL: https://issues.jboss.org/browse/ERT-16 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Max Rydahl Andersen > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > Add a command on the containers to run the "Docker exec" command that would rely on the Eclipse Terminal (org.eclipse.tm) (see bug 471672) to let the user run commands. > The command handler might open a dialog to confirm which command to run. By default it could be "/bin/bash" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-85) Remove ES levels from validation [EBZ#488346]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-85?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan closed ERT-85. --------------------------- Resolution: Duplicate Issue > Remove ES levels from validation [EBZ#488346] > --------------------------------------------- > > Key: ERT-85 > URL: https://issues.jboss.org/browse/ERT-85 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > Currently JSDT allows selection of ES level on JavaScript projects. This can be seen on the project properties> Validation. However only ES3 is supported at this time. I think it makes sense to remove the validation level completely from JSDT projects since we clearly do not support multiple ES levels. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-92) Pushing images fail (missing credentials) [EBZ#481629]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-92: -------------------------------------- Summary: Pushing images fail (missing credentials) [EBZ#481629] Key: ERT-92 URL: https://issues.jboss.org/browse/ERT-92 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon (4.6) Created attachment 257796 Error message when credentials are missing Pushing to DockerHub requires a <user>/<repo> name for the image (one cannot push to root of Docker Hub registry) Then, credentials input seems to be missing, as the operation fails with a "access not authorized" error -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-20) Pushing images fail (missing credentials) [EBZ#481629]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-20?page=com.atlassian.jira.plugin.sys... ] Nick Boldt updated ERT-20: -------------------------- Fix Version/s: Neon (4.6) > Pushing images fail (missing credentials) [EBZ#481629] > ------------------------------------------------------ > > Key: ERT-20 > URL: https://issues.jboss.org/browse/ERT-20 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Max Rydahl Andersen > Labels: Docker, bzira > Fix For: Neon (4.6) > > > Created attachment 257796 > Error message when credentials are missing > Pushing to DockerHub requires a <user>/<repo> name for the image (one cannot push to root of Docker Hub registry) > Then, credentials input seems to be missing, as the operation fails with a "access not authorized" error -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-83) com.google.gson is required but not named in any feature.xml [EBZ#487768]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-83?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-83: ---------------------------- Sprint: devex #3 February 2016 > com.google.gson is required but not named in any feature.xml [EBZ#487768] > ------------------------------------------------------------------------- > > Key: ERT-83 > URL: https://issues.jboss.org/browse/ERT-83 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > The bundle org.eclipse.wst.jsdt.js.npm had a dependency on com.google.gson, but that google bundle from Orbit is not mentioned by the enclosing feature org.eclipse.wst.jsdt.nodejs.feature. > This was found by doing a P2 mirror operation of the WTP repository and finding that com.google.gson was not brought along for the ride. > Though an install from the WTP repository will find the bundle and work, it's important for the feature to name the dependency also so that in the future if a patch is required on com.google.gson, we can create a feature patch to insert a newer version. This will be appreciated by those doing support in the future. > It will also mean that a mirror operation will bring along the proper set of dependencies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-82) Add JUnit Tests for JSON Editor [EBZ#486238]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-82?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-82: ---------------------------- Sprint: devex #3 February 2016 > Add JUnit Tests for JSON Editor [EBZ#486238] > -------------------------------------------- > > Key: ERT-82 > URL: https://issues.jboss.org/browse/ERT-82 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: bzira, wst.json > > We need to add JUnit Tests for JSON Editor. > The source for the core JUnit tests may be https://github.com/angelozerr/eclipse-wtp-json/tree/master/core/org.eclip... authored by Angelo Zerr (the author of JSON Editor). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-83) com.google.gson is required but not named in any feature.xml [EBZ#487768]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-83?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-83: ---------------------------- Story Points: 1 > com.google.gson is required but not named in any feature.xml [EBZ#487768] > ------------------------------------------------------------------------- > > Key: ERT-83 > URL: https://issues.jboss.org/browse/ERT-83 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > The bundle org.eclipse.wst.jsdt.js.npm had a dependency on com.google.gson, but that google bundle from Orbit is not mentioned by the enclosing feature org.eclipse.wst.jsdt.nodejs.feature. > This was found by doing a P2 mirror operation of the WTP repository and finding that com.google.gson was not brought along for the ride. > Though an install from the WTP repository will find the bundle and work, it's important for the feature to name the dependency also so that in the future if a patch is required on com.google.gson, we can create a feature patch to insert a newer version. This will be appreciated by those doing support in the future. > It will also mean that a mirror operation will bring along the proper set of dependencies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-82) Add JUnit Tests for JSON Editor [EBZ#486238]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-82?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-82: ---------------------------- Story Points: 2 > Add JUnit Tests for JSON Editor [EBZ#486238] > -------------------------------------------- > > Key: ERT-82 > URL: https://issues.jboss.org/browse/ERT-82 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: bzira, wst.json > > We need to add JUnit Tests for JSON Editor. > The source for the core JUnit tests may be https://github.com/angelozerr/eclipse-wtp-json/tree/master/core/org.eclip... authored by Angelo Zerr (the author of JSON Editor). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21796) [bzira] [jiralint] HTTP 400 errors creating ERT JIRAs from Eclipse BZ when BZ is in ASSIGNED state

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21796?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21796: ------------------------------- Summary: [bzira] [jiralint] HTTP 400 errors creating ERT JIRAs from Eclipse BZ when BZ is in ASSIGNED state (was: [bzira] [jiralint] 400 errors creating ERT JIRAs from Eclipse BZ) > [bzira] [jiralint] HTTP 400 errors creating ERT JIRAs from Eclipse BZ when BZ is in ASSIGNED state > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-21796 > URL: https://issues.jboss.org/browse/JBIDE-21796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: bzira.log.txt > > > Was reported today that Eclipse bugzilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=488373 was not created as an ERT issue. > So I re-ran bzira like this: > {code} > python -W ignore bzira.py -u JIRA_USER -p JIRA_PWD -s https://issues.jboss.org -S 2016-02-24 -v > {code} > And got this when creating ERT-82: > {code} > [INFO] Created https://issues.jboss.org/browse/ERT-82 > JiraError HTTP 400 > text: It seems that you have tried to perform a workflow operation (Start Progress) that is not valid for the current state of this issue (ERT-82). The likely cause is that somebody has changed the issue recently, please look at the issue history for details. > url: https://issues.jboss.org/rest/api/2/issue/ERT-82/transitions > {code} > Curiously, the same error was thrown when creating ERT-88: > {code} > [INFO] Created https://issues.jboss.org/browse/ERT-88 > > Jira ERT-82 gave following errors: > Could not perform transition{'id': '4'} error: JiraError HTTP 400 > text: It seems that you have tried to perform a workflow operation (Start Progress) that is not valid for the current state of this issue (ERT-82). The likely cause is that somebody has changed the issue recently, please look at the issue history for details. > url: https://issues.jboss.org/rest/api/2/issue/ERT-82/transitions > {code} > full log: [^bzira.log.txt] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-76) Sync of IJSONModel with editor should be improved/fixed [EBZ#486860]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-76?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-76: ---------------------------- Sprint: devex #2 February 2016 (was: devex #2 February 2016, devex #3 February 2016) > Sync of IJSONModel with editor should be improved/fixed [EBZ#486860] > -------------------------------------------------------------------- > > Key: ERT-76 > URL: https://issues.jboss.org/browse/ERT-76 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Nick Boldt > Assignee: Victor Rubezhny > Labels: bzira, wst.json > Fix For: Neon (4.6) M6 > > > IMHO the sync of IJSONModel with editor is the most important and should be done/fixed before fixing, improving other features. But it is the most hard too. > At first, we should validate the IJSONModel API > The big problem with JSON Editor is that the IJSONModel, IJSONPair, IJSONDocument, etc. There are a lot of copy/paste from XML/CSS plugins so this model and the implementation should be really fixed/improved. > For instance completion works when editor is opened, but it is broken after some changes of the text editor. It is because IJSONModel is not very well sync. > The most bugs that I see like: > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=486606 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=485694 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=486849 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=486524 > are linked to this sync problem. > So tests https://github.com/angelozerr/eclipse-wtp-json/blob/master/core/org.eclip... must be completed when sync of model is improved. > I will try to create a patch for adding tests https://bugs.eclipse.org/bugs/show_bug.cgi?id=486238 > It's a very hard task, so good luck to do that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 February 2016