One quirk. The swt support in org/eclipse/platform : org.eclipse.swt, started
using a environment var: osgi.platform, to include a choice of target swt impl.
The line in the pom for this now looks like:
<dependencies>
<dependency>
<groupId>org.eclipse.platform</groupId>
<artifactId>org.eclipse.swt.${osgi.platform}</artifactId>
<version>[3.105.3,3.105.3]</version>
</dependency>
</dependencies>
If you don't set this osgi.platform (e.g. mvn dependency:tree
-Dosgi.platform=win32.win32.x86_64 ), you get a complaint about unparsable
dependencies, or if you are using mvn install, and supply this, you get a
complaint about the version - it doesn't like [x.y.z, x.y.z] - identical version
numbers as the range.
The work-around is to continue to use the "old" style swt ref, not in
org/eclipse/platform groupId. The only version in maven central is 4.3, so the
upper bound was set to 5.0.0 )
<dependency>
<groupId>org.eclipse.swt</groupId>
<artifactId>org.eclipse.swt.win32.win32.x86</artifactId>
<version>[3.2.0,5.0.0)</version>
<scope>provided</scope>
</dependency>
-Marshall
Since this is a "provided" scope, only the API is being used, and it will work
with non-windows eclipse versions.
