File README.packaging of Package languagetool

Unfortunately, because dependencies are lazily evaluated at
build time, there is no clean and simple way to get a tarball of
vendored dependencies from Maven. The dependency plugin does not
work reliably either: It attempts to fetch dependencies that are
not required to build and not available in the remote repositories,
and fails to fetch some dependencies that are.

So in order to do this, you must run the %build steps on a local
checkout, and then package the resulting vendor directory.

Note that if the path to your checkout contains colons (:), the
build will most likely fail because the build system internally
uses that character as a path separator.

For now, only the HTTP API server and client are packaged because
these are the only build targets that have bundled dependencies
apart from languagetool-standalone, which builds the release zip
rather than something that can be installed.

Runtime version reporting is broken. It requires a proper .git
directory at build time. The minimal one provided by obs_scm does
not suffice, as the build system wants to retrieve detailed commit
information (including closest tags) and has no way to override
this behavior or provide the missing information when its tasks are
being skipped.

Further packaging efforts will require patching.
If you’re reading this, you’re very welcome to try :3