GitLab

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.

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

This allows correctly setting it to an absolute path based on the
project directory. The location of the secret key ring is not sensitive
information, so it does not need to be stored encrypted.

Previously the patchfiles were copied into the source of each
generated parser, even though they are identical for all parsers and
always use a hardcoded package name. This means that all generated
parsers had conflicting classes, although in practice this was not
noticeable, because the classes were always identical.

These common files are now a proper separate library that all
generated parsers will depend on. This will fix the class name
conflicts when using more than one SableCC parser in a single project.

archivesBaseName is already set to the project name by default.

Remove unneeded entries and sort remaining ones.

In almost all cases there should be no need for it. Users that do need
to use it can manually add it locally.

JDK 12 and higher only support targeting Java 7 and higher.

Builds should always be done using the Gradle wrapper to avoid version
issues, and the deploy task no longer exists (the standard Gradle
assemble task should be used instead).

It does basically the same thing as Gradle's standard build task.

rather than private
this allows to adapt line and pos
in derived lexers so that we do not start
parsing at line 0 and position 0.

Clean up and update build

This Gradle project has no subprojects, so the allprojects block is
unnecessary.

JDK 9 and higher only support targeting Java 6 and higher.