September 2016 - jbosstools-issues

[JBoss JIRA] (ERT-417) JSON Editor issues with Arrays [EBZ#501310]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-417?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-417: ---------------------------- Sprint: (was: devex #120 September 2016) > JSON Editor issues with Arrays [EBZ#501310] > ------------------------------------------- > > Key: ERT-417 > URL: https://issues.jboss.org/browse/ERT-417 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Labels: General, bzira > Fix For: Neon.2 (4.6) > > > The JSON Editor has issues with arrays: > 1. Unwanted alignment when inside array literal (similar to bug 356606) > 2. Formatting array structure changes the data content > Please see the video below that shows the issue: > https://www.youtube.com/watch?v=OIoazEDbANs -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-386) code formatter inserts line breaks after const qualifier [EBZ#399501]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-386?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-386: ------------------------------- Assignee: Victor Rubezhny (was: Angel Misevski) > code formatter inserts line breaks after const qualifier [EBZ#399501] > --------------------------------------------------------------------- > > Key: ERT-386 > URL: https://issues.jboss.org/browse/ERT-386 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Priority: Trivial > Labels: General, bzira > > for a code line like > const FOO = "bar"; > the code formatter inserts a line break after the const keyword, resulting in > const > FOO = "bar"; > While this simply looks ugly (to me) code verification reports a warning "Missing semicolon", so I get many nasty m,arkers on source files. > Please remove those line breaks or make them settable in the formatter settings. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23128) Eclipse Neon.1 JSDT Blog

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23128?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-23128: -------------------------------- Sprint: (was: devex #120 September 2016) > Eclipse Neon.1 JSDT Blog > ------------------------- > > Key: JBIDE-23128 > URL: https://issues.jboss.org/browse/JBIDE-23128 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, upstream, website > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.2.AM2 > > > Need to write blog about Neon.1 JSDT improvements. Tentative structure: > - Node.js Debugger improvements > - New JavaScript Debugger > - npm scripts support > - OMPH installer support > - Important bug fixes (provide a query with all Neon.1 bug fixes) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-358) Replace traces of old parser in Search/Indexing code. [EBZ#498371]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-358?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-358: ---------------------------- Story Points: 10 (was: 25) > Replace traces of old parser in Search/Indexing code. [EBZ#498371] > ------------------------------------------------------------------ > > Key: ERT-358 > URL: https://issues.jboss.org/browse/ERT-358 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Angel Misevski > Priority: Trivial > Labels: General, bzira > > Search and Indexing should be changed to use the newer dom ASTParser, instead of the old parser (e.g. in org.eclipse.wst.jsdt.internal.core.search.indexing.SourceIndexer). > This needs to happen before any other improvements/refinements to JSDT Search. > Looking at org.eclipse.wst.jsdt.internal.compiler.SourceElementParser, most of the class is using deprecated code. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-358) Replace traces of old parser in Search/Indexing code. [EBZ#498371]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-358?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-358: ---------------------------- Sprint: devex #118 July 2016, devex #121 October 2016 (was: devex #118 July 2016, devex #120 September 2016) > Replace traces of old parser in Search/Indexing code. [EBZ#498371] > ------------------------------------------------------------------ > > Key: ERT-358 > URL: https://issues.jboss.org/browse/ERT-358 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Angel Misevski > Priority: Trivial > Labels: General, bzira > > Search and Indexing should be changed to use the newer dom ASTParser, instead of the old parser (e.g. in org.eclipse.wst.jsdt.internal.core.search.indexing.SourceIndexer). > This needs to happen before any other improvements/refinements to JSDT Search. > Looking at org.eclipse.wst.jsdt.internal.compiler.SourceElementParser, most of the class is using deprecated code. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18725) HTML Validation: Ability to perform custom validation for tags, attributes and attribute values in WTP

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18725?page=com.atlassian.jira.plugi... ] Victor Rubezhny updated JBIDE-18725: ------------------------------------ Sprint: devex #121 October 2016 (was: devex #120 September 2016) > HTML Validation: Ability to perform custom validation for tags, attributes and attribute values in WTP > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18725 > URL: https://issues.jboss.org/browse/JBIDE-18725 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html-source-editing, upstream > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Labels: new_and_noteworthy > Fix For: 4.3.x > > > WTP HTML validator marks any custom html tags as unknown. It's possible to disable this validation at all: Window->Preferences->Web->HTML Files->Validation ==> Set Elements -> Unknown tag name severity to "Ignore": > But these days there are many frameworks provide an ability to create custom tags and attributes, so there cannot be some static schema created in order to help to validate such pages. > We need to add a possibility to provide a custom validator for tags/attributes/values for WTP, so it could be called to validate a page elements. > See discussions here: JBIDE-18387 and here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=443097. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-329) Use Closure compiler [EBZ#497249]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-329?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-329: ---------------------------- Story Points: 15 (was: 25) > Use Closure compiler [EBZ#497249] > --------------------------------- > > Key: ERT-329 > URL: https://issues.jboss.org/browse/ERT-329 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Gorkem Ercan > Labels: 3.9, General, bzira > Fix For: Oxygen (4.7) > > > Take closure compiler into use instead of the Esprima Parser to creates ASTs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-22225: -------------------------------- Sprint: devex #118 July 2016, devex #121 October 2016 (was: devex #118 July 2016, devex #120 September 2016) > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: debugging, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-329) Use Closure compiler [EBZ#497249]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-329?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-329: ---------------------------- Sprint: devex #118 July 2016, devex #121 October 2016 (was: devex #118 July 2016, devex #120 September 2016) > Use Closure compiler [EBZ#497249] > --------------------------------- > > Key: ERT-329 > URL: https://issues.jboss.org/browse/ERT-329 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Gorkem Ercan > Labels: 3.9, General, bzira > Fix For: Oxygen (4.7) > > > Take closure compiler into use instead of the Esprima Parser to creates ASTs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-383) JSONEditor: NPE when working with an array of objects [EBZ#497261]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-383?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-383: ---------------------------- Sprint: devex #121 October 2016 (was: devex #120 September 2016) > JSONEditor: NPE when working with an array of objects [EBZ#497261] > ------------------------------------------------------------------ > > Key: ERT-383 > URL: https://issues.jboss.org/browse/ERT-383 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Labels: bzira, wst.json > Fix For: Neon.2 (4.6) > > > I have not been able to reproduce this consistently, but here it goes: > Create a JSON file with following content: > { > "thirdaddition": true, > "name": "JSONEditorTest2", > "secondaddition": 2, > "description": "JSONEditorTest description2", > "version": "1.0.1", > "main": "app.js", > "scripts": { > "start": "node app.js" > }, > "array_of_objects": [{"abc": 1234}, {"value": 1234 }]]}}}}}}]}], > "value": "test", > "anothervalue": "1234" > } > When adding and removing (invalid) closing brackets, then modifying the value of the second array element (value), I tend to see this exception: > java.lang.NullPointerException > at org.eclipse.wst.json.core.internal.document.JSONModelParser.changeAttrValue(JSONModelParser.java:89) > at org.eclipse.wst.json.core.internal.document.JSONModelParser.changeRegion(JSONModelParser.java:131) > at org.eclipse.wst.json.core.internal.document.JSONModelImpl.regionChanged(JSONModelImpl.java:654) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:542) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1180) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1964) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) > at org.eclipse.jface.text.projection.ProjectionTextStore.replace(ProjectionTextStore.java:103) > at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1094) > at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1119) > at org.eclipse.jface.text.projection.ProjectionDocument.replace(ProjectionDocument.java:625) > at org.eclipse.jface.text.DefaultDocumentAdapter.replaceTextRange(DefaultDocumentAdapter.java:233) > at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7374) > at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:8225) > at org.eclipse.swt.custom.StyledText.doBackspace(StyledText.java:2334) > at org.eclipse.swt.custom.StyledText.invokeAction(StyledText.java:7164) > at org.eclipse.swt.custom.StyledText.handleKey(StyledText.java:6022) > at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:6049) > at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5733) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4248) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1538) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1534) > at org.eclipse.swt.widgets.Canvas.sendKeyEvent(Canvas.java:515) > at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1090) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5817) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSResponder.interpretKeyEvents(NSResponder.java:68) > at org.eclipse.swt.widgets.Composite.keyDown(Composite.java:610) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5727) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227) > at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2140) > at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2402) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5789) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5218) > at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5367) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3695) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 September 2016