February 2016 - jbosstools-issues

[JBoss JIRA] (ERT-83) com.google.gson is required but not named in any feature.xml [EBZ#487768]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-83: -------------------------------------- Summary: 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 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-84) Create oomph configuration to simplify development environment setup [EBZ#488343]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-84: -------------------------------------- Summary: Create oomph configuration to simplify development environment setup [EBZ#488343] Key: ERT-84 URL: https://issues.jboss.org/browse/ERT-84 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot Would be good to have JSDT project available in eclipse-installer distribution. That would let potential contributors to configure development environment, get sources and start hacking the code much faster then doing all development setup manually. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 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 resolved ERT-14. ----------------------------- Resolution: Done > [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 > Assignee: Shane Bryzak > 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)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-85) Remove ES levels from validation [EBZ#488346]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-85: -------------------------------------- Summary: Remove ES levels from validation [EBZ#488346] Key: ERT-85 URL: https://issues.jboss.org/browse/ERT-85 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot Currently JSDT allows selection of ES level on JavaScript projects. This can be seen on the project properties> Validation. However only ES3 is supported at this time. I think it makes sense to remove the validation level completely from JSDT projects since we clearly do not support multiple ES levels. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-86) Remove ECMAScript Compliance level from project properties [EBZ#488373]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-86: -------------------------------------- Summary: Remove ECMAScript Compliance level from project properties [EBZ#488373] Key: ERT-86 URL: https://issues.jboss.org/browse/ERT-86 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot This option can be found under Project properties -> JavaScript -> Validation. This setting should be removed, and ES6 supported by default. Currently the highest available version that can be set by this property is ES3. -- 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 Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-87: -------------------------------------- Summary: 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 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-88) Exception when checking package.json/bower.json [EBZ#488648]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-88: -------------------------------------- Summary: 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 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

[JBoss JIRA] (ERT-82) Add JUnit Tests for JSON Editor [EBZ#486238]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-82: -------------------------------------- Summary: 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 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-74) JSON Editor feature is uncategorized in the update site [EBZ#487038]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-74?page=com.atlassian.jira.plugin.sys... ] Victor Rubezhny updated ERT-74: ------------------------------- Sprint: devex #3 February 2016 > JSON Editor feature is uncategorized in the update site [EBZ#487038] > -------------------------------------------------------------------- > > Key: ERT-74 > URL: https://issues.jboss.org/browse/ERT-74 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: bzira, wst.json > > The JSON Editor feature can not be found under http://download.eclipse.org/webtools/downloads/drops/R3.8.0/S-3.8.0M5-201..., unless "Group items by category" is unchecked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21794) Can't create new JIRA from AERI webapp

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21794?page=com.atlassian.jira.plugi... ] Marcel Bruch resolved JBIDE-21794. ---------------------------------- Fix Version/s: 4.3.1.CR1 Resolution: Done Please retry. > Can't create new JIRA from AERI webapp > -------------------------------------- > > Key: JBIDE-21794 > URL: https://issues.jboss.org/browse/JBIDE-21794 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri > Reporter: Fred Bricon > Assignee: Marcel Bruch > Fix For: 4.3.1.CR1 > > > When trying to create a new JIRA from the AERI webapp, after selecting the project, the component and version contain irrelevant values: > http://screencast.com/t/lsQydPTusV > Creating a new ticket then fails > Typing unlisted values in those lists is then ignored, so there really is no way for me to open JIRAs from AERI incidents -- 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