You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!--- Provide a brief summary of the issue in the title above -->
4
+
5
+
### Expected Behavior
6
+
<!--- If you're describing a bug, tell us what should happen -->
7
+
<!--- If you're suggesting a change/improvement, tell us how it should work -->
8
+
9
+
### Current Behavior
10
+
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
11
+
<!--- If suggesting a change/improvement, explain the difference from current behavior -->
12
+
13
+
14
+
15
+
<!-- The following needs to be completed as best as possible **for bugs only** -->
16
+
### Steps to Reproduce (for bugs only)
17
+
<!-- If describing a bug, please include the **full** configuration of the plugin -->
18
+
<!-- If describing a bug, is there a (public) project where this issue can be reproduced? -->
19
+
<!-- If describing a bug, please include any stack-traces or any error messages -->
20
+
21
+
### Environment (for bugs only)
22
+
<!-- If describing a bug, please provide the plugin version is being used -->
23
+
<!-- If describing a bug, please provide the Java-Version is being used (please include details about oracle-jdk VS open-jdk) -->
24
+
<!-- If describing a bug, please provide the Maven-Version is being used (output of ``mvn --version``) -->
25
+
<!-- If describing a bug, please let us know on what Operating System you experience the bug (on Linux run ``lsb_release -a``) -->
26
+
<!-- If describing a bug, please let us know in what context maven is being executed (e.g. inside Windows Terminal, Powershell, Git Bash, /bin/bash, ...) -->
27
+
<!-- If describing a bug, please let us know how maven is being executed (e.g. ``mvn clean deploy`` VS ``mvn deploy:deploy``) -->
Copy file name to clipboardExpand all lines: README.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -472,6 +472,7 @@ It's really simple to setup this plugin; below is a sample pom that you may base
472
472
-->
473
473
<forceLongFormat>false</forceLongFormat>
474
474
</gitDescribe>
475
+
475
476
<!-- @since 2.2.2 -->
476
477
<!--
477
478
Since version **2.2.2** the maven-git-commit-id-plugin comes equipped with an additional validation utility which can be used to verify if your project properties are set as you would like to have them set.
@@ -495,13 +496,29 @@ It's really simple to setup this plugin; below is a sample pom that you may base
495
496
</validationProperty>
496
497
<!-- the next validationProperty you would like to validate -->
497
498
</validationProperties>
499
+
498
500
<!-- @since 2.2.2 -->
499
501
<!--
500
502
true by default, controls whether the validation will fail if *at least one* of the validationProperties does not match with it's expected values.
501
503
If you don't care about this, you may want to set this value to false (this makes the configuration of validationProperties useless).
502
504
*Note*: This configuration will only be taken into account when the additional goal `validateRevision` is configured inside an execution and at least one validationProperty is defined.
Allow to tell the plugin what commit should be used as reference to generate the properties from.
511
+
By default this property is simply set to `HEAD` which should reference to the latest commit in your repository.
512
+
513
+
In general this property can be set to something generic like `HEAD^1` or point to a branch or tag-name.
514
+
To support any kind or use-case this configuration can also be set to an entire commit-hash or it's abbreviated version.
515
+
516
+
A use-case for this feature can be found in https://github.com/ktoso/maven-git-commit-id-plugin/issues/338.
517
+
518
+
Please note that for security purposes not all references might be allowed as configuration.
519
+
If you have a specific use-case that is currently not white listed feel free to file an issue.
520
+
-->
521
+
<evaluateOnCommit>HEAD</evaluateOnCommit>
505
522
</configuration>
506
523
507
524
</plugin>
@@ -882,6 +899,7 @@ Optional parameters:
882
899
883
900
*Note*: Depending on your plugin configuration you obviously can choose the 'prefix' of your properties by setting it accordingly in the plugin's configuration. As a result this is therefore only an illustration what the switch means when the 'prefix' is set to it's default value.
884
901
*Note*: If you set the value to something that's not equal to 'flat' or 'full' (ignoring the case) the plugin will output a warning and will fallback to the default 'flat' mode.
902
+
***evaluateOnCommit** - `(default: HEAD)`*(available since v2.2.4)* Allow to tell the plugin what commit should be used as reference to generate the properties from. By default this property is simply set to `HEAD` which should reference to the latest commit in your repository. In general this property can be set to something generic like `HEAD^1` or point to a branch or tag-name. To support any kind or use-case this configuration can also be set to an entire commit-hash or it's abbreviated version. Please note that for security purposes not all references might be allowed as configuration. If you have a specific use-case that is currently not white listed feel free to file an issue.
885
903
886
904
**gitDescribe**:
887
905
Worth pointing out is, that git-commit-id tries to be 1-to-1 compatible with git's plain output, even though the describe functionality has been reimplemented manually using JGit (you don't have to have a git executable to use the plugin). So if you're familiar with [git-describe](https://github.com/ktoso/maven-git-commit-id-plugin#git-describe---short-intro-to-an-awesome-command), you probably can skip this section, as it just explains the same options that git provides.
0 commit comments