Description Leo Ufimtsev 2017-12-07 10:10:03 EST

During development, building a *swt*.jar file (containing fresh SWT*.java sources and .so's) that can be used with an eclipse in it's eclipse/plugin/ is not straight forward.  (As me, Roland and Eric have found out).

Example use case is testing/developing swt behavior as a OSGI bundle.

The general technique is:
cd ~/git/eclipse.platform.swt.binaries/bundles/org.eclipse.swt.gtk.linux.x86_64
mvn clean verify -Pbuild-individual-bundles

But the hurdle here is that if the *swt.binaries/bundles/binaries-parent/pom.xml:forceContextQualifier is as new as the one upstream, then changes to swt sources are not packaged into the resulting ./target/*swt*.jar file.
To get around that, I can either checkout an older swt.binaries that has an older forceContextQualifier or change the forceContextQualifier manually to something like year 2000.

Rather than documentation that is hard to find/read, I wrote a script that automatically sets a lower forceContextQualifier and builds the *swt*.jar files.