tree 6c3ed05f598be0626780288d7726f4cbe6681b6b
parent 958c19ac1b3dc392d6a4f0ec466c0cd9e554e738
author Krisztián Szűcs <szucs.krisztian@gmail.com> 1618513100 +0200
committer Krisztián Szűcs <szucs.krisztian@gmail.com> 1618513100 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQFOBAABCAA4FiEEOOW2r8dr6sA77zHlgjqBKYe1QKUFAmB4jMwaHHN6dWNzLmty
 aXN6dGlhbkBnbWFpbC5jb20ACgkQgjqBKYe1QKWxXAgAqL2EDxnhBiiiZLVZwVuJ
 gQlxxzqMUPOFZhDQB2JFUfzuDCb0zBSsGmRp5Q0rK9OM483t04K3tmCCNWPfXbVQ
 a7uXERUAfJXIJ6eDNeG43F0czELgEun9oBhjajzFKl+oTurY/Z+sW47bWMxHfu3K
 4ctBCpnfFmMGeUTv4Ui03UEY+uaQrTFHM5EOp9EHv23Dgybl+FzcS3gHZEV78lXc
 kkLbCSLF6p7uiwnTymiGR/iyO0Txr2jsDPhdrRgU1DGnhGW3bi43VVd7Pi6jDlS7
 JadJRiXVApi9BpbF/l/vGel7UxYFmxpevwN3X+/rG/5Y3a13ZvfNzfokcGiHJEWV
 Qg==
 =98fr
 -----END PGP SIGNATURE-----

ARROW-6103: [Release][Java] Remove mvn release plugin

We want to stop using the maven release plugin because it commits to the repo both in the `prepare` and `perform` tasks and adds complexity to the release process.

This PR removes the plugin and updates the release preparation script to use the maven versions plugin to update the version number in the pom files.

We will need to run `mvn deploy` to publish the artifacts and I'm not sure where that needs to happen (`mvn release:perform` was previously invoking the `deploy` phase).

Closes #9155 from andygrove/remove-mvn-release-plugin

Lead-authored-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
Co-authored-by: Andy Grove <andygrove73@gmail.com>
Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>