February 2016 - jbosstools-issues

[JBoss JIRA] (ERT-55) Need to add navigation from Project Explorer to Editor for grunt tasks [EBZ#486241]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-55?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-55: ---------------------------- Sprint: (was: devex #1 February 2016) > Need to add navigation from Project Explorer to Editor for grunt tasks [EBZ#486241] > ----------------------------------------------------------------------------------- > > Key: ERT-55 > URL: https://issues.jboss.org/browse/ERT-55 > 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 > > Original Estimate: 1 day, 2 hours > Remaining Estimate: 1 day, 2 hours > > Grunt task selection in Project Explorer should highlight task in the Editor if the suitable file is opened. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-54) Need to add navigation from Project Explorer to Editor for gulp tasks [EBZ#486240]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-54?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-54: ---------------------------- Sprint: devex #1 February 2016 > Need to add navigation from Project Explorer to Editor for gulp tasks [EBZ#486240] > ---------------------------------------------------------------------------------- > > Key: ERT-54 > URL: https://issues.jboss.org/browse/ERT-54 > 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 > > Original Estimate: 1 day, 2 hours > Remaining Estimate: 1 day, 2 hours > > Gulp task selection in Project Explorer should highlight task in the Editor if the suitable file is opened. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-55) Need to add navigation from Project Explorer to Editor for grunt tasks [EBZ#486241]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-55?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-55: ---------------------------- Sprint: devex #1 February 2016 > Need to add navigation from Project Explorer to Editor for grunt tasks [EBZ#486241] > ----------------------------------------------------------------------------------- > > Key: ERT-55 > URL: https://issues.jboss.org/browse/ERT-55 > 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 > > Original Estimate: 1 day, 2 hours > Remaining Estimate: 1 day, 2 hours > > Grunt task selection in Project Explorer should highlight task in the Editor if the suitable file is opened. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-4) Ignore undefined HTML attributes, elements validation with extension point [EBZ#443097]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-4?page=com.atlassian.jira.plugin.syst... ] Victor Rubezhny updated ERT-4: ------------------------------ Story Points: 1 > Ignore undefined HTML attributes, elements validation with extension point [EBZ#443097] > --------------------------------------------------------------------------------------- > > Key: ERT-4 > URL: https://issues.jboss.org/browse/ERT-4 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Max Rydahl Andersen > Assignee: Victor Rubezhny > Labels: bzira, wst.html > Fix For: Neon (4.6) M6 > > > I'm developping a plugin for AngularJS https://github.com/angelozerr/angularjs-eclipse which is based on WTP. > I have implemented validation for Angular which ignores (ng-* attributes, etc) with Java code without using your feature https://bugs.eclipse.org/bugs/show_bug.cgi?id=415980 > But there is some limitation and it should be fantastic if WTP provides an extension point like this : > --------------------------------------------------- > public interface IHTMLIgnoreValidator { > boolean shouldValidateAttributeName(IProject project, Element target, String attrName); > boolean shouldValidateElementName((IProject project, Element target); > } > --------------------------------------------------- > For more information please read https://github.com/angelozerr/angularjs-eclipse/issues/80#issuecomment-53... > https://bugs.eclipse.org/bugs/show_bug.cgi?id=415980 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-4) Ignore undefined HTML attributes, elements validation with extension point [EBZ#443097]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-4?page=com.atlassian.jira.plugin.syst... ] Victor Rubezhny reassigned ERT-4: --------------------------------- Assignee: Victor Rubezhny (was: Konstantin Marmalyukov) > Ignore undefined HTML attributes, elements validation with extension point [EBZ#443097] > --------------------------------------------------------------------------------------- > > Key: ERT-4 > URL: https://issues.jboss.org/browse/ERT-4 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Max Rydahl Andersen > Assignee: Victor Rubezhny > Labels: bzira, wst.html > Fix For: Neon (4.6) M6 > > > I'm developping a plugin for AngularJS https://github.com/angelozerr/angularjs-eclipse which is based on WTP. > I have implemented validation for Angular which ignores (ng-* attributes, etc) with Java code without using your feature https://bugs.eclipse.org/bugs/show_bug.cgi?id=415980 > But there is some limitation and it should be fantastic if WTP provides an extension point like this : > --------------------------------------------------- > public interface IHTMLIgnoreValidator { > boolean shouldValidateAttributeName(IProject project, Element target, String attrName); > boolean shouldValidateElementName((IProject project, Element target); > } > --------------------------------------------------- > For more information please read https://github.com/angelozerr/angularjs-eclipse/issues/80#issuecomment-53... > https://bugs.eclipse.org/bugs/show_bug.cgi?id=415980 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-4) Ignore undefined HTML attributes, elements validation with extension point [EBZ#443097]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-4?page=com.atlassian.jira.plugin.syst... ] Victor Rubezhny updated ERT-4: ------------------------------ Sprint: devex #1 February 2016 > Ignore undefined HTML attributes, elements validation with extension point [EBZ#443097] > --------------------------------------------------------------------------------------- > > Key: ERT-4 > URL: https://issues.jboss.org/browse/ERT-4 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Labels: bzira, wst.html > Fix For: Neon (4.6) M6 > > > I'm developping a plugin for AngularJS https://github.com/angelozerr/angularjs-eclipse which is based on WTP. > I have implemented validation for Angular which ignores (ng-* attributes, etc) with Java code without using your feature https://bugs.eclipse.org/bugs/show_bug.cgi?id=415980 > But there is some limitation and it should be fantastic if WTP provides an extension point like this : > --------------------------------------------------- > public interface IHTMLIgnoreValidator { > boolean shouldValidateAttributeName(IProject project, Element target, String attrName); > boolean shouldValidateElementName((IProject project, Element target); > } > --------------------------------------------------- > For more information please read https://github.com/angelozerr/angularjs-eclipse/issues/80#issuecomment-53... > https://bugs.eclipse.org/bugs/show_bug.cgi?id=415980 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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: ---------------------------- Sprint: devex #1 February 2016 > [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 > 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)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21613) NPE if click on failed CDK server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21613?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-21613: ----------------------------------- Assignee: Rob Stryker > NPE if click on failed CDK server > --------------------------------- > > Key: JBIDE-21613 > URL: https://issues.jboss.org/browse/JBIDE-21613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > I ran my CDK server but it failed by timeout (it tool longer than the timeout to start the server). > When the server finally started (I saw it in the console) I clicked on the server in the server view to "restart" it. You don't need to start/stop the server. Just click on/select the server in the view: > {code} > java.lang.NullPointerException > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.findDockerConnection(CDKDockerUtility.java:53) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:111) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:188) > at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:203) > at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144) > at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:158) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:155) > at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2178) > at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1717) > at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1069) > at org.eclipse.ui.navigator.CommonViewer.setSelection(CommonViewer.java:368) > at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:383) > at org.eclipse.wst.server.ui.internal.cnf.ServerDecoratorsHandler$1.run(ServerDecoratorsHandler.java:58) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1132) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1023) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:651) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:595) > 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:497) > 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) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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: ---------------------------- Sprint: (was: devex #1 February 2016) > [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 > 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)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-14) [ES6] Support for ECMAScript 6 syntax coloration [EBZ#477030]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-14?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-14: ---------------------------- Sprint: devex #1 February 2016 > [ES6] Support for ECMAScript 6 syntax coloration [EBZ#477030] > ------------------------------------------------------------- > > Key: ERT-14 > URL: https://issues.jboss.org/browse/ERT-14 > 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 > > > It should be cool if JSDT could support ECMAScript 6 syntax coloration like highlight "let", "const" etc keywords, template string, etc > To do that there are 2 solutions : > * delegate this syntax coloration to another component, like I have done with acorn parser. See https://github.com/angelozerr/tern.java/issues/310 and https://github.com/angelozerr/tern.java/tree/master/sandbox > * improve the existing org.eclipse.wst.jsdt.internal.ui.text.java.JavaCodeScanner to support ES6 syntax coloration (I think it will be a better solution). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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