At work, I am currently trying to set up commitizen on a handful of Java libraries and am not sure the best option to choose on cz init regarding the source of the version.

• Maybe the commitizen config option would be fine, since I'm already adding the toml
• npm is out of the question since it seems unnecessary to have to add a package.json to a Java project
• Also, eventually, I want to be able to have cz run in our Azure DevOps pipeline whenever we are creating a release from develop to master

This led me to consider extending the selections to include Maven's pom.xml and be able to both get AND set the project.version

This seems possible by invoking maven directly from the command line via a subprocess in python:

import subprocess
def run_cmd(command):
 return subprocess.Popen(command, shell=True, stdout=subprocess.PIPE).stdout.read()
version_cmd='mvn help:evaluate -Dexpression=project.version -q -DforceStdout'
version = run_cmd(version_cmd)
print(version.decode())

If this looks like an okay starting point, I can create a PR with a first stab at the commitizen/providers/maven_provider.py file.

Not sure what else will need to update yet though, so any guidance would be welcome!