then a properties file, FILE, will be generated with the jgitver info properties.
This enables such properties to be picked up by the remainder of the CI pipeline.
Design choices:
I've opted for a System Property to control this rather than an element in config file. The reason is that for the moment - for existing config options - the distinction seems to be that config file configures jigitver (the library) while System Properties configure the maven extension. I wanted to be compliant with that tradition.
If the file cannot be written it is considered a breaking error for the Maven execution. The rationale is: If user has specified this sysprop he surely has an expectation that it will be created.
Furthermore this PR
ads Integration test case (verify-export-properties)
Amends README in order to document the new feature (and adds documentation about what the jgitver.used_version property means although not related directly to this PR)
New feature: If
jgitver.export-properties-path=FILEis defined as a System Property, for example on the command line:then a properties file,
FILE, will be generated with the jgitver info properties.This enables such properties to be picked up by the remainder of the CI pipeline.
Design choices:
jigitver(the library) while System Properties configure the maven extension. I wanted to be compliant with that tradition.Furthermore this PR
verify-export-properties)jgitver.used_versionproperty means although not related directly to this PR)Fixes #163