Semantic Versioning looks like a sensible attempt to bring some order to the chaos of software versioning.
... until the collector arrives ...
Under Windows, an attempt to run an application as another user may fail for obvious reasons, such as the target user lacks sufficient permissions for the operation in question. There is at least one less obvious reason why this operation will fail: the Secondary Logon service must be running. Less obvious to me, at least.
I have an Eclipse "sandbox" project that I use to test little SWT snippets. While trying to run one such snippet after upgrading to Eclipse Juno (4.2.0), I got the following exception:
The snippet worked prior to the upgrade. I checked my classpath and the org.eclipse.core.runtime JAR was in the list. It turns out that many of the classes in the package org.eclipse.core.runtime are now in the org.eclipse.equinox.common JAR.
Using BIRT 4.2.0 on Windows, rotated chart text is sometimes garbled. One way to reproduce the problem is to rotate the labels on a chart axis:
FontDefinition font = xAxis.getLabel().getCaption().getFont(); font.setName("MS Sans Serif"); font.setRotation(45);
The resulting axis labels might look something like this:
The problem does not always occur. It appears to be sensitive to the chosen font. MS Sans Serif seems to fail reliably. That is one of the few raster fonts left on Windows. Is that a clue as to the nature of the bug?.
In my case, the application was using
JFaceResources.getBannerFont(). This font is determined by a property setting from one of the operating system-specific resource files in the
org.eclipse.jface package. Windows 7 and Vista are configured to use Segoe UI (which works). Windows XP and 2000 use Tahoma, which also works. All server versions of Windows fall back to a generic Windows property file that uses MS Sans Serif. This means that the bug could manifest itself on all typical server installations (such as the Citrix server on which the bug bit me).
I wonder if this is a bug in BIRT, JFace, SWT or GDI? It is logged in the Eclipse bug database as bug 377825.
- ▼ Aug 2012 (4)
- ► 2011 (8)
- ► 2010 (25)
- ► 2009 (51)
- ► 2008 (78)
- ► 2007 (94)
- ► 2006 (135)
- ► 2005 (58)
- ► 2004 (68)
- ► 1999 (10)