November 2016 - jbosstools-issues

[JBoss JIRA] (ERT-433) Invalid octal escape sequence (\8) causes IllegalArgumentException [EBZ#501790]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-433?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-433: ----------------------------- Sprint: devex #123 November 2016 (was: devex #122 October 2016) > Invalid octal escape sequence (\8) causes IllegalArgumentException [EBZ#501790] > ------------------------------------------------------------------------------- > > Key: ERT-433 > URL: https://issues.jboss.org/browse/ERT-433 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Priority: Critical > Labels: General, bzira > > Created attachment 264269 > Stack Trace > Any file containing a string with '\8' or '\9' in it will cause an IllegalArgumentException whenever ASTParser executes on it. This prevents the JavaScript editor from being initialized, preventing normal opening of the file. > '\#' in pre ES5 is used to denote an octal escape sequence, and so \8 and \9 are indeed invalid, but this should be reported as an error in the file. > The error is thrown in org.eclipse.wst.jsdt.core.util.JsStringScanner#scanEscape() and is not caught. > To reproduce: create a new JavaScript file, add the line `var x = "\8"` to it, > and attempt to save the file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-424) ClassCastException in JSONModelParser.insertValue [EBZ#502183]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-424?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-424: ----------------------------- Sprint: devex #123 November 2016 (was: devex #122 October 2016) > ClassCastException in JSONModelParser.insertValue [EBZ#502183] > -------------------------------------------------------------- > > Key: ERT-424 > URL: https://issues.jboss.org/browse/ERT-424 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: bzira, wst.json > > The following problem was reported via the automated error reporting: > Message: org.eclipse.wst.json.core.internal.document.JSONDocumentImpl cannot be cast to org.eclipse.wst.json.core.internal.document.JSONPairImpl > java.lang.ClassCastException: org.eclipse.wst.json.core.internal.document.JSONDocumentImpl cannot be cast to org.eclipse.wst.json.core.internal.document.JSONPairImpl > at org.eclipse.wst.json.core.internal.document.JSONModelParser.insertValue(JSONModelParser.java:904) > at org.eclipse.wst.json.core.internal.document.JSONModelParser.insertStructuredDocumentRegion(JSONModelParser.java:854) > at org.eclipse.wst.json.core.internal.document.JSONModelParser.replaceStructuredDocumentRegions(JSONModelParser.java:1706) > at org.eclipse.wst.json.core.internal.document.JSONModelImpl.handleRefresh(JSONModelImpl.java:411) > at org.eclipse.wst.json.core.internal.document.JSONModelImpl.nodesReplaced(JSONModelImpl.java:599) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:600) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1198) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1979) > 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.doContent(StyledText.java:2530) > at org.eclipse.swt.custom.StyledText.handleKey(StyledText.java:6018) > 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) > Bundles: > | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 | > | org.eclipse.e4.core.di | 1.6.0.v20160319-0612 | 1.6.0.v20160319-0612 | > | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 | > | org.eclipse.jface.text | 3.11.0.v20160505-1301 | 3.11.0.v20160505-1301 | > | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 | > | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 | > | org.eclipse.wst.json.core | 1.0.100.v201608161657 | 1.0.100.v201608161657 | > | org.eclipse.wst.sse.core | 1.1.1000.v201608061824 | 1.1.1000.v201608061824 | > | org.eclipse.wst.sse.ui | 1.3.500.v201605120129 | 1.3.500.v201605120129 | > Operating Systems: > | Windows | 6.3.0 | 6.3.0 | > The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/57dd6... for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. > Created on behalf of vrubezhny(a)xxxxxx.xxx -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23477) Remove the occurrences of org.jboss.tools.hibernate.runtime.spi.ISettings

by Koen Aers (JIRA)

Koen Aers created JBIDE-23477: --------------------------------- Summary: Remove the occurrences of org.jboss.tools.hibernate.runtime.spi.ISettings Key: JBIDE-23477 URL: https://issues.jboss.org/browse/JBIDE-23477 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Affects Versions: 4.4.2.AM3 Reporter: Koen Aers -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-428) On projects with builders JavaScript Validator and Validation xml files are validated twice and error markers are duplicated [EBZ#495625]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-428?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-428: ----------------------------- Sprint: devex #123 November 2016 (was: devex #122 October 2016) > On projects with builders JavaScript Validator and Validation xml files are validated twice and error markers are duplicated [EBZ#495625] > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: ERT-428 > URL: https://issues.jboss.org/browse/ERT-428 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: General, bzira > > When a project has enabled builders JavaScript Validator and Validation, org.eclipse.wst.xml.core.internal.validation.eclipse.Validator is called twice from org.eclipse.wst.validation.internal.ValManager and all results are summed. As the result, validation error messages are duplicated. > ValBuilderJob.runInWorkspace() has a loop in which it repeats validation until getRequest() returns null. Then ValManager.validate(IProject,...) calls delete markers, but it works only for the first call, it is designed to accumulate markers created in multiple calls from ValBuilderJob during the same build. > Two requests that make the same file to be validated twice come independently from > 1) org.eclipse.wst.validation.internal.operations.ValidationBuilder > 2) org.eclipse.wst.jsdt.internal.core.builder.JavaBuilder > by method newBuild(). > When I disable JavaScript Validator in project properties in section Builders, there is no more duplication of markers. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23321) Integration tests for OpenShift Node.js debugger

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23321?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-23321: --------------------------------- Sprint: devex #123 November 2016 (was: devex #122 October 2016) > Integration tests for OpenShift Node.js debugger > ------------------------------------------------- > > Key: JBIDE-23321 > URL: https://issues.jboss.org/browse/JBIDE-23321 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, openshift > Affects Versions: 4.4.2.AM1 > Reporter: Ilya Buziuk > Assignee: Pavol Srna > Fix For: 4.4.2.Final > > > Node.js Debugging support implemented as part of https://issues.jboss.org/browse/JBIDE-22225 > Should be covered with red deer integration tests. Basically, test coverage of Node.js Debugger facilities already covered with red deer in JSDT project - https://git.eclipse.org/r/#/c/82836/ > However, implementing smth. similar for OpenShift will be much trickier. Basically, there is an integration test *org.jboss.tools.openshift.ui.bot.test.application.v3.adapter.PublishChangesTest* which is used for server adapter publishing. For now this test is not sustainable due to https://issues.jboss.org/browse/JBIDE-23005 . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-389) TypeScript debugging [EBZ#487465]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-389?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-389: ----------------------------- Sprint: devex #123 November 2016 (was: devex #122 October 2016) > TypeScript debugging [EBZ#487465] > --------------------------------- > > Key: ERT-389 > URL: https://issues.jboss.org/browse/ERT-389 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Priority: Trivial > Labels: Debug, bzira > > I'm developping a TypeScript plugins based on JSDT & tsserver https://github.com/angelozerr/typescript.java and it should be very cool if JSDT debugger could debug TypeScript (by using source map). > If you are interested to work together about integration TypeScript (with JSDT), I have created an issue at https://github.com/angelozerr/typescript.java/issues/2. > Please note that TypEcs support debugging with Eclipse https://github.com/axmor/typecs/tree/master/src/com.axmor.eclipse.typescr... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

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

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-329?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-329: ----------------------------- Sprint: devex #118 July 2016, devex #123 November 2016 (was: devex #118 July 2016, devex #122 October 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 (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-214) Validate JSON file with JSON Schema [EBZ#494111]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-214?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-214: ----------------------------- Story Points: 5 (was: 10) > Validate JSON file with JSON Schema [EBZ#494111] > ------------------------------------------------ > > Key: ERT-214 > URL: https://issues.jboss.org/browse/ERT-214 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Priority: Trivial > Labels: bzira, wst.json > Fix For: Neon.2 (4.6) > > > It's a very big task, but it should be fantastic if WTP Validator could validate JSON file by using JSON Schema. > To do that: > * JSONSchemaDocument should support the full specification of JSON Schema. > * minimal-json should be improved to collect line, column or perhaps we could use IJSONDocument to validate it with JSON Schema. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23470) Server Adapter: stuck restarting in debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23470?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23470: ------------------------------------- Story Points: 8 Sprint: devex #123 November 2016 > Server Adapter: stuck restarting in debug mode > ---------------------------------------------- > > Key: JBIDE-23470 > URL: https://issues.jboss.org/browse/JBIDE-23470 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.2.Final > > Attachments: failed-to-detect-pod.png, server-adapter-stuck-starting.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

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

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-329?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-329: ----------------------------- Story Points: 5 (was: 15) > 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 (v7.2.3#72005)

9 years, 5 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 November 2016