The "finally" block will always run, in ordinary code. All the ways of skipping it are dubious, to various extents.
The least bad way is to exit the whole Java Virtual Machine using System.exit(). This is not deprecated, but code that uses System.exit() may be difficult to re-use. Inappropriate use of System.exit() in applications that write to files, network or database may cause corruption.
Even worse ways to skip "finally" would involve using deprecated methods like Thread.stop(), evil operations using native code via JNI, provoking JVM crashes, killing the Java process via an external system tool etc.
Basically, avoid doing any of the above and you can then, in all but the most sensitive applications, assume "finally" will always run.
Betty Rubble? Well, I would go with Betty... but I'd be thinking of Wilma.
The finally block will always run when the try block completes normally or abruptly.
Only way to not run finally is to make the try block not complete at all by using infinite loop, infinite wait, System.exit(), ... Thread.stop() does not work since it uses an exception (ThreadDeath by default) to stop the Thread and that exception is handled as any other exception.