https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

The Gradle documentation says that these convention properties are
deprecated and superseded by the java and application extension blocks.
Using the convention properties doesn't generate warnings yet, but it
can't hurt to switch to the now recommended way.

This doesn't affect predicates passed to :exec/:constants/:init yet,
because ProB 2's StateSpace.transitionFromPredicate method currently
only accepts a string predicate (which is parsed using the model's
languate) and not an arbitrary IEvalElement.

This fixes a bug where interrupting a command would terminate the main
event loop thread, causing the kernel to stop responding. This happened
because the interrupt handling sent a Java interrupt to the thread
executing the current command, which was always the main event loop
thread. Now commands are executed on a separate executor, which can
safely have Java interrupts sent to it without affecting any
jupyter-jvm-basekernel threads.

When an error points to an external file, its source code is now read
and errors highlighted in it.

Error highlighting for code from the last load cell now also works when
an error pointing to it is thrown in a later cell (although this
doesn't happen often). The initial/default machine is also recognized
(although there should never be errors pointing to its code).

At the moment error highlighting is only supported for the
machine/formula in the current cell.

This significantly improves the performance of loading new machines.

If the cursor is after the command name, but before the start of the
argument string, it makes more sense from a user perspective to treat
it as if it was at the start of the argument string. This way if there
are multiple spaces between the command name and argument, the user can
still use code completion inside this whitespace and get completions
for the first parameter of the command.

This makes it possible to inspect B variables when the cursor is right
before the first character of the identifier.

There is now a single preprocessInput method that is responsible for
adding a command prefix to any input that doesn't already have one.
This simplifies the implementations of (eval|inspect|complete)Internal
somewhat, because they can now assume that the input (after
preprocessing) always starts with a command name.

This code was effectively never called - in Jupyter Notebook, pressing
Tab on a whitespace-only line will add an indent level rather than
triggering code completion.

The PositionedString offsets here now use the same origin as the "at"
index received from Jupyter. This way the "at" index and the
replacements no longer need to be offset manually after the command
name is removed from the string.

The PositionedString offsets here now use the same origin as the "at"
index received from Jupyter. This way the "at" index no longer needs to
be offset manually after the command name is removed from the string.

This position information isn't used for anything yet.