[JBoss JIRA] (JBIDE-20834) Fix issues with styled label providers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20834?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-20834 at 12/4/15 10:23 AM:
--------------------------------------------------------------------
Great, thanks! This solves JBIDE-21141 as one can see in the screenshots:
!openshift2-grey-decorations.png!
!openshift3-grey-decorations.png!
was (Author: adietish):
Great, thanks! This solves JBIDE-21141 as one can see in the screenshots:
!openshift2-grey-decorations.png!
!openshift3-grey-decorations.png!
> Fix issues with styled label providers
> --------------------------------------
>
> Key: JBIDE-20834
> URL: https://issues.jboss.org/browse/JBIDE-20834
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.3.0.CR1
> Reporter: Snjezana Peco
> Assignee: Andre Dietisheim
> Fix For: 4.4.0.Alpha1
>
> Attachments: openshift2-grey-decorations.png, openshift3-grey-decorations.png
>
>
> Since https://bugs.eclipse.org/bugs/show_bug.cgi?id=466499 has been fixed, we can remove the workaround related to styled label providers.
> The fix is included in Mars 4.5.1 (Mars.1) and Neon 4.6.0M2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20753) Text flickering when selecting server types in New Server wizard
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20753?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-20753:
---------------------------------------
Sorry to hear you can't replicate. For the record, I showed it to Radim Hopp yesterday and he saw it on his computer also (Fedora I believe).
> Text flickering when selecting server types in New Server wizard
> ----------------------------------------------------------------
>
> Key: JBIDE-20753
> URL: https://issues.jboss.org/browse/JBIDE-20753
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: regression
> Fix For: 4.3.x, 4.4.0.Alpha1
>
>
> When you open the New Server wizard and select a server type, There will be some elements rendered for a fraction of a second. It's Server Runtime Environment and a dropdown menu - it will disappear again, but it's not nice to see something quickly appear and disappear again. You can keep selecting server types and it will keep happening. All of this is on the first page of the dialog.
> I checked and this did not happen in Beta2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21170) Virtualbox could not be found by CDK adapter
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21170?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-21170 at 12/4/15 9:38 AM:
----------------------------------------------------------------
BTW, here's a link describing how you can force launchd to use some path, but it's not really an option for us:
http://stackoverflow.com/questions/25385934/setting-environment-variables...
Alternatively, one could also use launchctl setenv PATH ....., but I don't think that's something we can do either.
was (Author: mmalina):
BTW, here's a link describing how you can force launchd to use some path, but it's not really an option for us:
http://stackoverflow.com/questions/25385934/setting-environment-variables...
> 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
>
> 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, 4 months