add '-SNAPSHOT' to all versions that do not correspond to a release. Deprecated use 'strategy' instead.
Define the version strategy to use for the version resolution.
The policy to lookup the base tag that will be used for the version computation.
control how a base version is ued to calculate the new version, here the patch number of the version will be incremented. If version X.Y.Z is found as base version, then X.Y.(Z+1) will be used for the new version.
add a distance number from the base version as a version qualifier. For example if HEAD is 3 commit ahead the base version 1.0.0 then calculated version will be 1.0.0-3
add a 'dirty' qualifier if the version is calculated from a stale git directory (modified files, new files, ...)
if true and the dirty state is detected then make the build fail
appends a qualifier with the git sha1 of the HEAD commit, the length is controlled by the property 'gitCommitIdLength'
appends a qualifier with a git HEAD commit timestamp
comma separated list of branches for which no qualifier should be defined
java regular expression to find tags to extract version from, if omitted default value is used: v?([0-9]+(?:\.[0-9]+){0,2}(?:-[a-zA-Z0-9\-_]+)?)
Used only when strategy 'PATTERN' is used. Defines the pattern to compute the version for standard commits (ie commits not having any tag).
Used only when strategy 'PATTERN' is used. Defines the pattern to compute the version for tag commits (ie commits having one or more version-able tag).
relative path to a directory to be excluded by jgitver. Paths are relative to the base multi module directory of the maven project.
java regex pattern that will match branch name. The regex pattern to be valid MUST contain a unique group selection.
a transformation to apply, value taken from fr.brouillard.oss.jgitver.BranchingPolicy#BranchNameTransformations
List of available strategies.
List of available LookupPolicies.
The reachable tag with highest version-able value will be used for basis of computation.
The latest, by date, tag with will be used for basis of computation.
The nearest, i.e. the one with lowest depth from HEAD, tag with will be used for basis of computation. In case of equal depth, the LATEST of equal depth tags is used.