February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21797) Fails to start the CDK server when it's was already started from CLI

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21797?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21797: ------------------------------------- I initially had the wrong cdk vagrantfile selected in the server settings vs the one started in CLI. But Even after fixing that and making sure the cdk is the proper one, it still fails > Fails to start the CDK server when it's was already started from CLI > -------------------------------------------------------------------- > > Key: JBIDE-21797 > URL: https://issues.jboss.org/browse/JBIDE-21797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI > - once it's started, start the same CDK from the CDK server adapter > => the server should detect the CDK already started and should simply be put in started mode, instead it fails to start with > !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21793) Zero-click import of CDK

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21793?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21793: ------------------------------------- [~maxandersen] Um... care to comment on this? It seems this would require that we disable the runtime detection dialog on startup? That'd be a material change to the feature, and I'd like your +1 before pursuing. > Zero-click import of CDK > ------------------------ > > Key: JBIDE-21793 > URL: https://issues.jboss.org/browse/JBIDE-21793 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.3.1.Beta2 > Reporter: Pete Muir > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > When the installer with the CDK completes and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server. > We should try to import the CDK with no-clicks, and hide the detection dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21782) Adding EAP 7. ER6 server rises a warning on New runtime page

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21782?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21782: -------------------------------- Fix Version/s: 4.3.1.CR1 > Adding EAP 7. ER6 server rises a warning on New runtime page > ------------------------------------------------------------ > > Key: JBIDE-21782 > URL: https://issues.jboss.org/browse/JBIDE-21782 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > Screenshot: http://i.imgur.com/ObzrfQs.png > The warning is: > {noformat} > This server type expects a version of 6.1 but the server directory is of version 7.0.0.GA. This combination may cause critical errors. {noformat} > I guess it's because ER6 reports version "7.0.0.GA". > For example ER2 doesn't raise the warning (because it still reports as 7.0.0.Beta1). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21797) Fails to start the CDK server when it's was already started from CLI

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21797?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21797: ----------------------------------- Assignee: Rob Stryker > Fails to start the CDK server when it's was already started from CLI > -------------------------------------------------------------------- > > Key: JBIDE-21797 > URL: https://issues.jboss.org/browse/JBIDE-21797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI > - once it's started, start the same CDK from the CDK server adapter > => the server should detect the CDK already started, and should simply be put in started mode, instead it fails to start with > !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21797) Fails to start the CDK server when it's was already started from CLI

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21797?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21797: -------------------------------- Fix Version/s: 4.3.1.CR1 > Fails to start the CDK server when it's was already started from CLI > -------------------------------------------------------------------- > > Key: JBIDE-21797 > URL: https://issues.jboss.org/browse/JBIDE-21797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI > - once it's started, start the same CDK from the CDK server adapter > => the server should detect the CDK already started, and should simply be put in started mode, instead it fails to start with > !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21797) Fails to start the CDK server when it's was already started from CLI

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21797?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21797: -------------------------------- Description: - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI - once it's started, start the same CDK from the CDK server adapter => the server should detect the CDK already started and should simply be put in started mode, instead it fails to start with !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650! was: - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI - once it's started, start the same CDK from the CDK server adapter => the server should detect the CDK already started, and should simply be put in started mode, instead it fails to start with !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650! > Fails to start the CDK server when it's was already started from CLI > -------------------------------------------------------------------- > > Key: JBIDE-21797 > URL: https://issues.jboss.org/browse/JBIDE-21797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI > - once it's started, start the same CDK from the CDK server adapter > => the server should detect the CDK already started and should simply be put in started mode, instead it fails to start with > !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21797) Fails to start the CDK server when it's was already started from CLI

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-21797: ----------------------------------- Summary: Fails to start the CDK server when it's was already started from CLI Key: JBIDE-21797 URL: https://issues.jboss.org/browse/JBIDE-21797 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk Affects Versions: 4.3.1.CR1 Reporter: Fred Bricon - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI - once it's started, start the same CDK from the CDK server adapter => the server should detect the CDK already started, and should simply be put in started mode, instead it fails to start with !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-81) o.e.w.j.c.i.d.JSONPairImpl cannot be cast to o.e.w.j.c.i.d.JSONObjectImpl [EBZ#487168]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-81?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan closed ERT-81. --------------------------- Resolution: Duplicate Issue > o.e.w.j.c.i.d.JSONPairImpl cannot be cast to o.e.w.j.c.i.d.JSONObjectImpl [EBZ#487168] > -------------------------------------------------------------------------------------- > > Key: ERT-81 > URL: https://issues.jboss.org/browse/ERT-81 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: bzira, wst.json > > Created attachment 259553 > JSON content causing the error > Whenever I type something in the JSON editor (content generated by openshift3/kubernetes, see attached foo.json file), the log fills with > !ENTRY org.eclipse.wst.json.core 4 4 2016-02-03 15:46:35.835 > !MESSAGE org.eclipse.wst.json.core.internal.document.JSONPairImpl cannot be cast to org.eclipse.wst.json.core.internal.document.JSONObjectImpl > !STACK 0 > java.lang.ClassCastException: org.eclipse.wst.json.core.internal.document.JSONPairImpl cannot be cast to org.eclipse.wst.json.core.internal.document.JSONObjectImpl > at org.eclipse.wst.json.core.internal.document.JSONModelParser.removeStructuredDocumentRegion(JSONModelParser.java:2500) > at org.eclipse.wst.json.core.internal.document.JSONModelParser.changeStructuredDocumentRegion(JSONModelParser.java:552) > at org.eclipse.wst.json.core.internal.document.JSONModelParser.changeRegion(JSONModelParser.java:354) > at org.eclipse.wst.json.core.internal.document.JSONModelImpl.regionChanged(JSONModelImpl.java:602) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:542) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1180) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1964) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) > at org.eclipse.jface.text.projection.ProjectionTextStore.replace(ProjectionTextStore.java:111) > at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1184) > at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210) > at org.eclipse.jface.text.projection.ProjectionDocument.replace(ProjectionDocument.java:629) > at org.eclipse.jface.text.DefaultDocumentAdapter.replaceTextRange(DefaultDocumentAdapter.java:248) > at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7305) > at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:8156) > at org.eclipse.swt.custom.StyledText.doBackspace(StyledText.java:2306) > at org.eclipse.swt.custom.StyledText.invokeAction(StyledText.java:7095) > at org.eclipse.swt.custom.StyledText.handleKey(StyledText.java:5968) > at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:5995) > at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5682) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1528) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1524) > at org.eclipse.swt.widgets.Canvas.sendKeyEvent(Canvas.java:496) > at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1060) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5784) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSResponder.interpretKeyEvents(NSResponder.java:68) > at org.eclipse.swt.widgets.Composite.keyDown(Composite.java:594) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21170) Problems with CDK Adapter resulting from missing PATH in Eclipse on Mac

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21170?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21170: ------------------------------------- The new PR works for me, Vagrant and Virtualbox are found on the path so, I can get the CDK started. > Problems with CDK Adapter resulting from missing PATH in Eclipse on Mac > ----------------------------------------------------------------------- > > Key: JBIDE-21170 > URL: https://issues.jboss.org/browse/JBIDE-21170 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > The problem is that CDK tooling relies on PATH to find vagrant. And the "vagrant up" command in turn depends on PATH to find e.g. VBoxManage. > On Mac, when you start your Eclipse / JBDS as an app by double-clicking an icon on your Desktop or in Finder, the Eclipse instance will have no PATH env variable. > One workaround is to start your Eclipse from command line by going inside the package: > {code} > cd Eclipse.app/Contents/MacOS > ./eclipse > {code} > But this is definitely not the recommended way to start Eclipse - I'm not sure if eclipse.ini is located properly in this case. But at least PATH is correct then. > There is actually one more workaround. To add your PATH to the Environment tab in Launch config. That works for me. > So that might be a potential solution to this problem - have a predefined PATH for each OS in case there is none defined in the Eclipse process. > After I set up a CDK server adapter and fixed the wrong path to vagrant in the launch config, I then started the server adapter and got this: > Server CDK Server Adapter at localhost failed to start. > Console: > {code} > The provider 'virtualbox' that was requested to back the machine > 'default' is reporting that it isn't usable on this system. The > reason is shown below: > Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed. > Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires > this to be available on the PATH. If VirtualBox is installed, please find the > `VBoxManage` binary and add it to the PATH environmental variable. > {code} > Along with this, there was an Unhandled event loop exception in the error view: > {code} > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > 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:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > 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:520) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > Caused by: java.lang.NullPointerException > at org.jboss.tools.central.editors.GettingStartedHtmlPage.updateEarlyAccess(GettingStartedHtmlPage.java:359) > at org.jboss.tools.central.editors.GettingStartedHtmlPage.access$14(GettingStartedHtmlPage.java:342) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$6$1.run(GettingStartedHtmlPage.java:327) > at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162) > at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > ... 23 more > {code} > In the command line, VBoxManage is accessible and it is located in /usr/local/bin/ and on my PATH. > Max suggested I could try to start Eclipse from command line instead of double-clicking in Finder (which is the normal way to do it on Mac) and that helped. > So for some reason when you start Eclipse using Eclipse.app from Finder, the PATH is incorrect. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-21) Update or replace JSDT parser to support ES6 [EBZ#481706]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-21?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-21: ---------------------------- Story Points: 25 (was: 40) > Update or replace JSDT parser to support ES6 [EBZ#481706] > --------------------------------------------------------- > > Key: ERT-21 > URL: https://issues.jboss.org/browse/ERT-21 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Priority: Trivial > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > > Support ecma-262 standard Javascript language features with the JSDT parser so that other functionality can provide relevant support -- 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