February 2016 - jbosstools-issues

[JBoss JIRA] (ERT-15) [ES6] Support for ECMAScript 6 validation [EBZ#477031]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-15?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-15: ---------------------------- Story Points: 15 (was: 50) > [ES6] Support for ECMAScript 6 validation [EBZ#477031] > ------------------------------------------------------ > > Key: ERT-15 > URL: https://issues.jboss.org/browse/ERT-15 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > > JSDT Validator doesn't support ES6 syntax and display a lot of error with ES6 syntax. > To fix this problem, there are 2 solutions : > * improve the JSDT Validator to support ES6 syntax (I think it's a lot of work). > * gives the capability to disable the JSDT Validator (with extension point and with preferences). With those solution, we could delegate the validator to another component like Tern JSHint (https://github.com/angelozerr/tern.java/wiki/Tern-Linter-JSHint) where JSHint is able to validate ES6 syntax. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-12) [language support] Add support for ECMAScript 2015 [EBZ#473559]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-12?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-12: ---------------------------- Story Points: 25 (was: 40) > [language support] Add support for ECMAScript 2015 [EBZ#473559] > --------------------------------------------------------------- > > Key: ERT-12 > URL: https://issues.jboss.org/browse/ERT-12 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Gorkem Ercan > Priority: Trivial > Labels: 3.8_M6, Web, bzira > Fix For: Neon (4.6) M6 > > > As ECMAScript 6 aka ECMAScript 2015 got officially released in June 2015[1], the JSDT validator should integrate a related compliance level. > There was also a request for supporting ECMAScript 4[2], which got never released, though, and that bug never got traction. So I thought I'd open up a new one. This bug should serve as a meta-bug for the different features introduced in ECMAScript 2015. > Sebastian > [1] http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf > [2] Bug 223131 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-12) [language support] Add support for ECMAScript 2015 [EBZ#473559]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-12?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-12: ---------------------------- Story Points: 40 (was: 25) > [language support] Add support for ECMAScript 2015 [EBZ#473559] > --------------------------------------------------------------- > > Key: ERT-12 > URL: https://issues.jboss.org/browse/ERT-12 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Gorkem Ercan > Priority: Trivial > Labels: 3.8_M6, Web, bzira > Fix For: Neon (4.6) M6 > > > As ECMAScript 6 aka ECMAScript 2015 got officially released in June 2015[1], the JSDT validator should integrate a related compliance level. > There was also a request for supporting ECMAScript 4[2], which got never released, though, and that bug never got traction. So I thought I'd open up a new one. This bug should serve as a meta-bug for the different features introduced in ECMAScript 2015. > Sebastian > [1] http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf > [2] Bug 223131 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-15) [ES6] Support for ECMAScript 6 validation [EBZ#477031]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-15?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-15: ---------------------------- Sprint: devex #3 February 2016 > [ES6] Support for ECMAScript 6 validation [EBZ#477031] > ------------------------------------------------------ > > Key: ERT-15 > URL: https://issues.jboss.org/browse/ERT-15 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > > JSDT Validator doesn't support ES6 syntax and display a lot of error with ES6 syntax. > To fix this problem, there are 2 solutions : > * improve the JSDT Validator to support ES6 syntax (I think it's a lot of work). > * gives the capability to disable the JSDT Validator (with extension point and with preferences). With those solution, we could delegate the validator to another component like Tern JSHint (https://github.com/angelozerr/tern.java/wiki/Tern-Linter-JSHint) where JSHint is able to validate ES6 syntax. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3645) Installation of JBoss Developer Studio to a network drive fails

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3645?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3645: ------------------------------------ Assignee: Denis Golovin > Installation of JBoss Developer Studio to a network drive fails > ---------------------------------------------------------------- > > Key: JBDS-3645 > URL: https://issues.jboss.org/browse/JBDS-3645 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.1.0.GA > Environment: * Windows Server 2012 > Reporter: Takayuki Konishi > Assignee: Denis Golovin > > A customer is trying to install 64 bit jboss developer studio 8.1 using java 1.8 64 bit on a network drive (32 bit) from their local 64 bit machine. > Installation failed with the error, see the attached error message: > {code} > !SESSION 2016-02-16 16:05:32.385 ----------------------------------------------- > eclipse.buildId=unknown > java.version=1.8.0_65 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US > Framework arguments: -roaming -r jar:file:///E:/downloads/jboss-devstudio-8.1.0.GA-installer-standalone.jar!/ -d E:\tools\eclipse\studio -p jbds -i com.jboss.devstudio.core.package,org.testng.eclipse.feature.group,org.eclipse.wst.jsdt.feature.patch.feature.group -profileProperties org.eclipse.update.install.features=true > Command-line arguments: -roaming -r jar:file:///E:/downloads/jboss-devstudio-8.1.0.GA-installer-standalone.jar!/ -d E:\tools\eclipse\studio -p jbds -i com.jboss.devstudio.core.package,org.testng.eclipse.feature.group,org.eclipse.wst.jsdt.feature.patch.feature.group -profileProperties org.eclipse.update.install.features=true > !ENTRY org.eclipse.equinox.p2.engine 4 4 2016-02-16 16:27:12.468 > !MESSAGE An error occurred while installing the items > !SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2016-02-16 16:27:12.468 > !MESSAGE session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.rse.subsystems.shells.telnet 1.2.300.201403100950, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction). > !SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2016-02-16 16:27:12.468 > !MESSAGE The artifact file for osgi.bundle,org.eclipse.rse.subsystems.shells.telnet,1.2.300.201403100950 was not found. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-87) Icons for JSON outline [EBZ#488606]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-87?page=com.atlassian.jira.plugin.sys... ] Victor Rubezhny reassigned ERT-87: ---------------------------------- Assignee: Victor Rubezhny > Icons for JSON outline [EBZ#488606] > ----------------------------------- > > Key: ERT-87 > URL: https://issues.jboss.org/browse/ERT-87 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: bzira, wst.json > > JSON editor's outline uses a single icon for all the nodes and it is the same icon as the editor's. We need different icons for JSON outlines. The icons should be different for different JSON node types (Object, Number, Boolean, String...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

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

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-89?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-89: ---------------------------- Story Points: 10 > 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 > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > Figure out the action plan for search after the new parser -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

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

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-90?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-90: ---------------------------- Story Points: 10 > 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 > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > Figure out what to do for refactoring and code manipulation -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3644) Document installer/cdk/devstudio basic workflow

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3644?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3644: --------------------------------- Fix Version/s: 9.1.0.GA > Document installer/cdk/devstudio basic workflow > ----------------------------------------------- > > Key: JBDS-3644 > URL: https://issues.jboss.org/browse/JBDS-3644 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 9.1.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-88) Exception when checking package.json/bower.json [EBZ#488648]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-88?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-88: ---------------------------- Story Points: 1 > Exception when checking package.json/bower.json [EBZ#488648] > ------------------------------------------------------------ > > Key: ERT-88 > URL: https://issues.jboss.org/browse/ERT-88 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > The following exception is logged when a project is closed. > !ENTRY org.eclipse.wst.jsdt.js.npm 4 0 2016-02-28 10:15:30.039 > !MESSAGE Resource '/AprokectTor' is not open. > !STACK 1 > org.eclipse.core.internal.resources.ResourceException: Resource '/AprokectTor' is not open. > at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:144) > at org.eclipse.core.internal.resources.Container.members(Container.java:239) > at org.eclipse.core.internal.resources.Container.members(Container.java:226) > at org.eclipse.wst.jsdt.js.common.util.WorkbenchResourceUtil.findFileRecursively(WorkbenchResourceUtil.java:166) > at org.eclipse.wst.jsdt.js.npm.util.NpmUtil.isPackageJsonExist(NpmUtil.java:41) > at org.eclipse.wst.jsdt.js.npm.internal.launch.tester.NpmLaunchTester.test(NpmLaunchTester.java:37) > at org.eclipse.core.internal.expressions.Property.test(Property.java:58) > at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:100) > at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) > at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:112) > at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) > at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:160) > at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) > at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:75) > at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) > at org.eclipse.core.internal.expressions.EnablementExpression.evaluate(EnablementExpression.java:55) > at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.evalEnablementExpression(LaunchShortcutExtension.java:281) > at org.eclipse.debug.ui.actions.ContextualLaunchAction.isApplicable(ContextualLaunchAction.java:287) > at org.eclipse.debug.ui.actions.ContextualLaunchAction.fillMenu(ContextualLaunchAction.java:218) > at org.eclipse.debug.ui.actions.ContextualLaunchAction$1.menuShown(ContextualLaunchAction.java:141) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4245) > 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.notifyListeners(Widget.java:1313) > at org.eclipse.jface.action.ActionContributionItem.copyMenu(ActionContributionItem.java:1243) > at org.eclipse.jface.action.ActionContributionItem.handleShowProxy(ActionContributionItem.java:1223) > at org.eclipse.jface.action.ActionContributionItem.lambda$7(ActionContributionItem.java:1186) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4245) > 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:1505) > at org.eclipse.swt.widgets.Menu.menuWillOpen(Menu.java:805) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5761) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSMenu.popUpContextMenu(NSMenu.java:77) > at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:267) > at org.eclipse.swt.widgets.Display.runPopups(Display.java:4146) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3688) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1118) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1019) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:691) > 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:150) > 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:670) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609) > at org.eclipse.equinox.launcher.Main.run(Main.java:1516) > at org.eclipse.equinox.launcher.Main.main(Main.java:1489) > !SUBENTRY 1 org.eclipse.core.resources 4 372 2016-02-28 10:15:30.039 > !MESSAGE Resource '/AprokectTor' is not open. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 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