I have concluded that Eclipse is a big ball o' WTF. So is Java as a whole, but you probably knew that already.
The Windows version of Eclipse apparently comes with a copy of Ant, which is not exposed for command-line use. I did eventually manage to figure out how to trigger an Ant build from within Eclipse. It then promptly complains that JAVA_HOME doesn't point at a JDK; its stated vale is pointing at a directory with "jre" in its name. I eventually found where Eclipse has a setting for which JRE is active, and changed it to the JDK sitting right next to the JRE. Ant then promptly complained that the JDK didn't contain some tools archive it needed. Manually setting the JAVA_HOME environment variable did bugger-all.
My Mac doesn't have Ant installed for command-line use either.
My primary Linux box *does* have Ant installed in the normal way. It - or the Java compiler, whichever - complained that the build was configured for too old a version of Java which was no longer supported. I updated it to 1.8. The build then succeeded. But I have to say "ant jar" to make it actually build the jar that I'm familiar with seeing.
When actually running the installer on that same Linux box, I get the splash screen for a few seconds, then a *segfault*. A segfault, in Java, which doesn't even use pointers. WTF. Oh wait, the error screed says the fault occurred in a section of C code "outside the VM". Well that's all right then. Not. The official build triggers the same segfault, as it happens.
So I can run the installer on Windows, but I can only build it on Linux. This is going to do wonders for my edit-compile-debug cycle latency.