February 2016 - jbosstools-issues

[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: ---------------------------- Sprint: devex #3 February 2016 > 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, 9 months

1
0
0 / 0

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

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-86?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-86: ---------------------------- Story Points: 15 > 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 > Labels: Debug, bzira > > 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, 9 months

1
0
0 / 0

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

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-86?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-86: ---------------------------- Sprint: devex #3 February 2016 > 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 > Labels: Debug, bzira > > 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, 9 months

1
0
0 / 0

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

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-87?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-87: ---------------------------- Story Points: 2 > 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 > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-16) Add "Exec" command on a container, using Eclipse Terminal [EBZ#479336]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-16?page=com.atlassian.jira.plugin.sys... ] Nick Boldt updated ERT-16: -------------------------- Fix Version/s: Neon (4.6) (was: Mars.1 (4.5)) > Add "Exec" command on a container, using Eclipse Terminal [EBZ#479336] > ---------------------------------------------------------------------- > > Key: ERT-16 > URL: https://issues.jboss.org/browse/ERT-16 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Max Rydahl Andersen > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > Add a command on the containers to run the "Docker exec" command that would rely on the Eclipse Terminal (org.eclipse.tm) (see bug 471672) to let the user run commands. > The command handler might open a dialog to confirm which command to run. By default it could be "/bin/bash" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-16) Add "Exec" command on a container, using Eclipse Terminal [EBZ#479336]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-16?page=com.atlassian.jira.plugin.sys... ] Nick Boldt updated ERT-16: -------------------------- Labels: 5.0.0 Docker bzira (was: 4.1.0 Docker bzira) > Add "Exec" command on a container, using Eclipse Terminal [EBZ#479336] > ---------------------------------------------------------------------- > > Key: ERT-16 > URL: https://issues.jboss.org/browse/ERT-16 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Max Rydahl Andersen > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > Add a command on the containers to run the "Docker exec" command that would rely on the Eclipse Terminal (org.eclipse.tm) (see bug 471672) to let the user run commands. > The command handler might open a dialog to confirm which command to run. By default it could be "/bin/bash" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

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

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-85?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan closed ERT-85. --------------------------- Resolution: Duplicate Issue > 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 > Labels: General, bzira > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-92) Pushing images fail (missing credentials) [EBZ#481629]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-92: -------------------------------------- Summary: Pushing images fail (missing credentials) [EBZ#481629] Key: ERT-92 URL: https://issues.jboss.org/browse/ERT-92 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon (4.6) Created attachment 257796 Error message when credentials are missing Pushing to DockerHub requires a <user>/<repo> name for the image (one cannot push to root of Docker Hub registry) Then, credentials input seems to be missing, as the operation fails with a "access not authorized" error -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-20) Pushing images fail (missing credentials) [EBZ#481629]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-20?page=com.atlassian.jira.plugin.sys... ] Nick Boldt updated ERT-20: -------------------------- Fix Version/s: Neon (4.6) > Pushing images fail (missing credentials) [EBZ#481629] > ------------------------------------------------------ > > Key: ERT-20 > URL: https://issues.jboss.org/browse/ERT-20 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Max Rydahl Andersen > Labels: Docker, bzira > Fix For: Neon (4.6) > > > Created attachment 257796 > Error message when credentials are missing > Pushing to DockerHub requires a <user>/<repo> name for the image (one cannot push to root of Docker Hub registry) > Then, credentials input seems to be missing, as the operation fails with a "access not authorized" error -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

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

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-83?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-83: ---------------------------- Sprint: devex #3 February 2016 > 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 > Labels: General, bzira > > 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, 9 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