Replies: 1 comment 1 reply
-
Hi! Thanks for this info, we recommend creating a new package for different version handlers. Here's an example on how to build a custom version provider: |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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.npm
is out of the question since it seems unnecessary to have to add a package.json to a Java projectcz
run in our Azure DevOps pipeline whenever we are creating a release fromdevelop
tomaster
This led me to consider extending the selections to include Maven's
pom.xml
and be able to both get AND set theproject.version
This seems possible by invoking maven directly from the command line via a subprocess in python:
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!
Beta Was this translation helpful? Give feedback.
All reactions