Closed issue by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/24617

Description:
The `apache-maven-bin` package is prebuilt, has files in `/opt`, but symlinks to its files in `/usr/bin`.

On the other hand, the `apache-maven` package has compiled java stuff in `/usr/share`, requires sourcing a profile file to get access to its tools, and if `apache-maven-bin` is installed at the same time, its tools will be first in the PATH anyway, so the profile doesn't really help.

Then, some packages have `apache-maven`, others `apache-maven-bin` in `hostmakedepends`.

IMO neither of these packages really fit the proper packaging guidelines. So my questions are:

- should  the maven binaries become alternatives, or should `apache-maven` become the preferred provider of maven stuff?
- should we move all templates to `apache-maven` (and potentially remove `apache-maven-bin`? Why is it in the repos?)