[JBoss JIRA] (JBIDE-21298) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21298?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21298:
------------------------------------
Slip from Beta1 respin-a to Beta2. Feel free to push the PR into 4.3.x and master, but NOT into 4.3.1.Beta1x branch.
> 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component
> ----------------------------------------------------------------------
>
> Key: JBIDE-21298
> URL: https://issues.jboss.org/browse/JBIDE-21298
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Critical
> Labels: testfailure
> Fix For: 4.3.0.Beta2, 4.4.0.Alpha1
>
>
> *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component:*
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m...
> # [org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest|http://jenkins...] (failing for 5 builds)
> [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for runtime-detection component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest : testLoadSaveRuntimePaths{color} (failing for 5 builds)
>
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.mars/62/testReport/org.jboss.tools.runtime.test/RuntimeDetectionFrameworkTest/testLoadSaveRuntimePaths}
> <case>
> <age>5</age>
> <className>org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest</className>
> <duration>0.0050</duration>
> <errorDetails>/qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1></errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: /qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.TestCase.assertEquals(TestCase.java:401)
> at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73)
> </errorStackTrace>
> <failedSince>58</failedSince>
> <name>testLoadSaveRuntimePaths</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> </case>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21298) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21298?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21298:
-------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.1.Beta1)
> 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component
> ----------------------------------------------------------------------
>
> Key: JBIDE-21298
> URL: https://issues.jboss.org/browse/JBIDE-21298
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Critical
> Labels: testfailure
> Fix For: 4.3.0.Beta2, 4.4.0.Alpha1
>
>
> *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component:*
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m...
> # [org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest|http://jenkins...] (failing for 5 builds)
> [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for runtime-detection component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest : testLoadSaveRuntimePaths{color} (failing for 5 builds)
>
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.mars/62/testReport/org.jboss.tools.runtime.test/RuntimeDetectionFrameworkTest/testLoadSaveRuntimePaths}
> <case>
> <age>5</age>
> <className>org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest</className>
> <duration>0.0050</duration>
> <errorDetails>/qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1></errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: /qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.TestCase.assertEquals(TestCase.java:401)
> at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73)
> </errorStackTrace>
> <failedSince>58</failedSince>
> <name>testLoadSaveRuntimePaths</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> </case>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21298) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21298?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21298:
-------------------------------
Labels: testfailure (was: respin-a testfailure)
> 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component
> ----------------------------------------------------------------------
>
> Key: JBIDE-21298
> URL: https://issues.jboss.org/browse/JBIDE-21298
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Critical
> Labels: testfailure
> Fix For: 4.3.0.Beta2, 4.4.0.Alpha1
>
>
> *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component:*
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m...
> # [org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest|http://jenkins...] (failing for 5 builds)
> [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for runtime-detection component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest : testLoadSaveRuntimePaths{color} (failing for 5 builds)
>
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.mars/62/testReport/org.jboss.tools.runtime.test/RuntimeDetectionFrameworkTest/testLoadSaveRuntimePaths}
> <case>
> <age>5</age>
> <className>org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest</className>
> <duration>0.0050</duration>
> <errorDetails>/qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1></errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: /qa/services/hudson/jboss-runtimes
> expected:<0> but was:<1>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.TestCase.assertEquals(TestCase.java:401)
> at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73)
> </errorStackTrace>
> <failedSince>58</failedSince>
> <name>testLoadSaveRuntimePaths</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> </case>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21323) EL Knowledge Base Problem with enums
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21323?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21323:
-----------------------------------
Fix Version/s: 4.4.x
> EL Knowledge Base Problem with enums
> ------------------------------------
>
> Key: JBIDE-21323
> URL: https://issues.jboss.org/browse/JBIDE-21323
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.0.Final
> Environment: Eclipse Mars.1 (4.5.1), Primefaces 5.x
> Reporter: Andrei Ivanov
> Priority: Minor
> Fix For: 4.4.x
>
>
> Enum properties and method are not recognized:
> In this case, {{label}} is recognized and shows up in the completion suggestions, but {{name()}} is not and marked as unrecognized.
> {code:xml}
> <p:dataTable value="#{page.dataModel}" var="managerData" lazy="true"
> rowStyleClass="#{managerData.status.label} labor-protection-#{managerData.status.name().replace('_', '-').toLowerCase()}">
> ...
> </p:dataTable>
> {code}
> {code:java}
> public enum SignOffStatus {
> VALID("Valid"),
> ALMOST_EXPIRED("Almost expired"),
> EXPIRED("Expired");
> private final String label;
> private SignOffStatus(String label) {
> this.label = label;
> }
> public String getLabel() {
> return label;
> }
> }
> {code}
> In a different page:
> {code:xml}
> <p:selectOneMenu value="#{instancePage.instanceCriteria.status}">
> <f:selectItem itemLabel="--select--" itemValue="#{null}" />
> <f:selectItems value="#{appBean.getStatuses()}" var="stat" itemLabel="#{stat.label}" />
> </p:selectOneMenu>
> {code}
> The enum has a {{getLabel()}} as the one above, but in this context it's not recognized ({{"name" cannot be resolved}}).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21323) EL Knowledge Base Problem with enums
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21323?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21323:
--------------------------------------
Assignee: Viacheslav Kabanovich
> EL Knowledge Base Problem with enums
> ------------------------------------
>
> Key: JBIDE-21323
> URL: https://issues.jboss.org/browse/JBIDE-21323
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.0.Final
> Environment: Eclipse Mars.1 (4.5.1), Primefaces 5.x
> Reporter: Andrei Ivanov
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.4.x
>
>
> Enum properties and method are not recognized:
> In this case, {{label}} is recognized and shows up in the completion suggestions, but {{name()}} is not and marked as unrecognized.
> {code:xml}
> <p:dataTable value="#{page.dataModel}" var="managerData" lazy="true"
> rowStyleClass="#{managerData.status.label} labor-protection-#{managerData.status.name().replace('_', '-').toLowerCase()}">
> ...
> </p:dataTable>
> {code}
> {code:java}
> public enum SignOffStatus {
> VALID("Valid"),
> ALMOST_EXPIRED("Almost expired"),
> EXPIRED("Expired");
> private final String label;
> private SignOffStatus(String label) {
> this.label = label;
> }
> public String getLabel() {
> return label;
> }
> }
> {code}
> In a different page:
> {code:xml}
> <p:selectOneMenu value="#{instancePage.instanceCriteria.status}">
> <f:selectItem itemLabel="--select--" itemValue="#{null}" />
> <f:selectItems value="#{appBean.getStatuses()}" var="stat" itemLabel="#{stat.label}" />
> </p:selectOneMenu>
> {code}
> The enum has a {{getLabel()}} as the one above, but in this context it's not recognized ({{"name" cannot be resolved}}).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21170) Virtualbox could not be found by CDK adapter
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21170?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21170:
-------------------------------------
Using the patch, I get, when starting the CDK server adapter :
{noformat}
No usable default provider could be found for your system.
Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.
The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.
If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
`vagrant up --provider=PROVIDER`, which should give you a more specific
error message for that particular provider.
{noformat}
> Virtualbox could not be found by CDK adapter
> --------------------------------------------
>
> Key: JBIDE-21170
> URL: https://issues.jboss.org/browse/JBIDE-21170
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: respin-a
> Fix For: 4.3.1.Beta1
>
>
> 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)
10 years, 3 months
[JBoss JIRA] (JBIDE-21170) Virtualbox could not be found by CDK adapter
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21170?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21170:
-------------------------------------
https://github.com/jbosstools/jbosstools-openshift/pull/852/ - PR to fix this issue.
The tl;dr is that when eclipse is launched via .app, it has no path environment variable. In this case, for mac only, we will call out to bash -c "echo $PATH" to get the full path variable. Since we do this via Runtime.exec() and do not pass in an environment at all, we get a clean pure path from the system to use in the event that eclipse somehow lacks one.
Later on we can use this path when overriding or adding environment variables and merging it with the existing environment pulled from eclipse.
Martin has tested this earlier today and verified it fixed his issue.
> Virtualbox could not be found by CDK adapter
> --------------------------------------------
>
> Key: JBIDE-21170
> URL: https://issues.jboss.org/browse/JBIDE-21170
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: respin-a
> Fix For: 4.3.1.Beta1
>
>
> 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)
10 years, 3 months