[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)
9 years, 10 months
[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)
9 years, 10 months
[JBoss JIRA] (JBDS-3598) Error while building Jboss developer studio 9.1.0 Beta 2 from source
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3598?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3598 at 2/29/16 3:00 PM:
-----------------------------------------------------------
First, we make the skip flag actually work in fetch-sources-from-manifests, so that can be skipped.
https://github.com/jbosstools/jbosstools-maven-plugins/pull/54/files?w=1
Then, we disable all the git source stuff so we can build from source zip w/o git metadata:
https://github.com/jbdevstudio/jbdevstudio-product/pull/367
Then, to build from a source zip, we need only do this:
{code}
wget http://download.jboss.org/jbosstools/static/mars/development/updates/core... -O /tmp/jbosstools-4.3.1.Beta2-updatesite-core.zip
wget http://www.jboss.org/download-manager/content/origin/files/sha256/16/1627...
unzip -d jboss-devstudio-9.1.0.Beta2-src jboss-devstudio-9.1.0.Beta2-src.zip
cd jboss-devstudio-9.1.0.Beta2-src/jboss-devstudio-9.1.0.Beta2-src/jbdevstudio-product-e313a21b1694f8635fa056390641aeef6d44f198/
mvn clean install \
-Djbosstools-site=jar:file:///tmp/jbosstools-4.3.1.Beta2-updatesite-core.zip\!/ \
-Plocal-sources
{code}
was (Author: nickboldt):
First, we make the skip flag actually work in fetch-sources-from-manifests, so that can be skipped.
https://github.com/jbosstools/jbosstools-maven-plugins/pull/54/files?w=1
Then, we disable all the git source stuff so we can build from source zip w/o git metadata:
https://github.com/jbdevstudio/jbdevstudio-product/pull/367
Then, to build from a source zip, we need only do this:
{code}
mvn clean install \
-Djbosstools-site=jar:file:///home/nboldt/tmp/jbosstools-4.3.1.Beta2-updatesite-core.zip\!/ \
-Plocal-sources
{code}
> Error while building Jboss developer studio 9.1.0 Beta 2 from source
> --------------------------------------------------------------------
>
> Key: JBDS-3598
> URL: https://issues.jboss.org/browse/JBDS-3598
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.1.0.Beta2
> Environment: RHEL 7.1 PPC64le and Ubuntu x86_64
> Maven - 3.3.9
> JDK - 1.8
> Reporter: Deepali Chourasia
> Assignee: Nick Boldt
> Fix For: 9.1.0.CR1, 10.0.0.Alpha1
>
> Attachments: Jboss_devstudio_9.1.0_Beta2_buildlog.txt
>
>
> I have downloaded jboss-devstudio-9.1.0.Beta2-src.zip and am building it from source.
> The build fails with the following error:
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-45) Hide Chromium JavaScript Debugger Virtual FS from Eclipse Workspace [EBZ#486057]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-45?page=com.atlassian.jira.plugin.sys... ]
Ilya Buziuk reassigned ERT-45:
------------------------------
Assignee: Ilya Buziuk
> Hide Chromium JavaScript Debugger Virtual FS from Eclipse Workspace [EBZ#486057]
> --------------------------------------------------------------------------------
>
> Key: ERT-45
> URL: https://issues.jboss.org/browse/ERT-45
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Max Rydahl Andersen
> Assignee: Ilya Buziuk
> Labels: Debug, bzira
>
> Chromium JavaScript Debugger by default expose scripts loaded in JavaScript VM through virtual file system. It looks like normal workspace project with name matches the launch configuration name.
> All interactions with VM are done through actions available on files in that virtual system.
> Ideally that virtual FS should not be exposed to user if project that targeted for debug is already presented in workspace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months