February 2016 - jbosstools-issues

[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)

8 years, 9 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)

8 years, 9 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)

8 years, 9 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)

8 years, 9 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)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-63) npm dependency content assist is broken [EBZ#486849]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-63?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-63: ---------------------------- Story Points: 5 (was: 10) > npm dependency content assist is broken [EBZ#486849] > ---------------------------------------------------- > > Key: ERT-63 > URL: https://issues.jboss.org/browse/ERT-63 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Labels: bzira, wst.json > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-91) bower dependency content assist is broken [EBZ#487888]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-91: -------------------------------------- Summary: bower dependency content assist is broken [EBZ#487888] Key: ERT-91 URL: https://issues.jboss.org/browse/ERT-91 Project: Eclipse Release Train Issue Type: Task Components: WTP Source Editing Reporter: Friendly Jira Robot Fix For: Neon (4.6) M7 The content assist has stopped working for me and started to constantly throw the exceptions (see below). The problem might be occurring because either the URL that is used to get the dependency proposals has stopped working or the site was/is just shut down for some purpose. But anyway, probably just the displaying such a stack trace in the console is not a proper way to notify a user on the problem. We should properly log it into the Error Log instead. The stack trace appearing in the console: !ENTRY org.eclipse.wst.json.ui 4 4 2016-02-16 06:51:31.376 !MESSAGE org.eclipse.json.provisonnal.com.eclipsesource.json.ParseException: Expected value at 1:0 !STACK 0 java.io.IOException: org.eclipse.json.provisonnal.com.eclipsesource.json.ParseException: Expected value at 1:0 at org.eclipse.json.http.HttpHelper.makeRequest(HttpHelper.java:74) at org.eclipse.wst.json.ui.contentassist.HttpCompletionProposalCollector.addProposals(HttpCompletionProposalCollector.java:28) at org.eclipse.wst.json.ui.internal.contentassist.CompletionProposalMatcher.addProposalsIfMatch(CompletionProposalMatcher.java:42) at org.eclipse.wst.json.ui.internal.contentassist.CompletionProposalCollectorsRegistryReader.addProposals(CompletionProposalCollectorsRegistryReader.java:62) at org.eclipse.wst.json.ui.internal.contentassist.JSONCompletionProposalComputer.collectProposalsFromExtensionPoint(JSONCompletionProposalComputer.java:56) at org.eclipse.wst.json.ui.internal.contentassist.JSONCompletionProposalComputer.addObjectKeyProposals(JSONCompletionProposalComputer.java:43) at org.eclipse.wst.json.ui.contentassist.AbstractJSONCompletionProposalComputer.computeObjectKeyProposals(AbstractJSONCompletionProposalComputer.java:197) at org.eclipse.wst.json.ui.contentassist.AbstractJSONCompletionProposalComputer.computeCompletionProposals(AbstractJSONCompletionProposalComputer.java:153) at org.eclipse.wst.json.ui.contentassist.AbstractJSONCompletionProposalComputer.computeCompletionProposals(AbstractJSONCompletionProposalComputer.java:82) at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:284) at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:290) at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.collectProposals(StructuredContentAssistProcessor.java:484) at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.computeCompletionProposals(StructuredContentAssistProcessor.java:255) at org.eclipse.wst.sse.ui.internal.contentassist.CompoundContentAssistProcessor.computeCompletionProposals(CompoundContentAssistProcessor.java:127) at org.eclipse.jface.text.contentassist.ContentAssistant$5.run(ContentAssistant.java:1904) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1902) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:573) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:570) at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:505) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:499) at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1720) at org.eclipse.wst.sse.ui.internal.StructuredTextViewer.doOperation(StructuredTextViewer.java:488) at org.eclipse.ui.texteditor.ContentAssistAction$1.run(ContentAssistAction.java:82) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.texteditor.ContentAssistAction.run(ContentAssistAction.java:80) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:122) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:286) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:507) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:558) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:378) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:324) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:86) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1550) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1328) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1353) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1338) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1365) at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:763) at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3317) at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:785) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1980) at org.eclipse.swt.widgets.Control.windowProc(Control.java:5590) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4717) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9279) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1225) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2425) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) at org.eclipse.equinox.launcher.Main.run(Main.java:1515) at org.eclipse.equinox.launcher.Main.main(Main.java:1488) Caused by: org.eclipse.json.provisonnal.com.eclipsesource.json.ParseException: Expected value at 1:0 at org.eclipse.json.provisonnal.com.eclipsesource.json.JsonParser.error(JsonParser.java:368) at org.eclipse.json.provisonnal.com.eclipsesource.json.JsonParser.expected(JsonParser.java:361) at org.eclipse.json.provisonnal.com.eclipsesource.json.JsonParser.readValue(JsonParser.java:97) at org.eclipse.json.provisonnal.com.eclipsesource.json.JsonParser.parse(JsonParser.java:62) at org.eclipse.json.provisonnal.com.eclipsesource.json.JsonValue.readFrom(JsonValue.java:91) at org.eclipse.json.http.HttpHelper.makeRequest(HttpHelper.java:70) ... 87 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-90) Spike for refactoring and code manipulation

by Gorkem Ercan (JIRA)

Gorkem Ercan created ERT-90: ------------------------------- Summary: Spike for refactoring and code manipulation Key: ERT-90 URL: https://issues.jboss.org/browse/ERT-90 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Gorkem Ercan Figure out what to do for refactoring and code manipulation -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-89) Spike for changes on JSDT Search

by Gorkem Ercan (JIRA)

Gorkem Ercan created ERT-89: ------------------------------- Summary: Spike for changes on JSDT Search Key: ERT-89 URL: https://issues.jboss.org/browse/ERT-89 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Gorkem Ercan Figure out the action plan for search after the new parser -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21796) [bzira] [jiralint] 400 errors creating ERT JIRAs from Eclipse BZ

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21796?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21796: ------------------------------------ This could be caused by the fact that Eclipse BZ https://bugs.eclipse.org/bugs/show_bug.cgi?id=486238 is in "ASSIGNED" state, and the ERT JIRA can't be set to "Coding in progress" via REST API. > [bzira] [jiralint] 400 errors creating ERT JIRAs from Eclipse BZ > ---------------------------------------------------------------- > > 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)

8 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2016