At present, the maven tasks use "mvn deploy" in the release pipeline. This pushes packages to the maven registry, which may be useful in some situations, but in many situations, these packages will never be used and simply take up space. We could add an "mvn install" step, which does the same, but without pushing packages. Then each user could modify the pipeline in the builds and select if they want to use "mvn install" or "mvn deploy".