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
Copy file name to clipboardExpand all lines: README.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -366,7 +366,15 @@ It's really simple to setup this plugin; below is a sample pom that you may base
366
366
367
367
<!-- Only consider tags matching the given pattern. This can be used to avoid leaking private tags from the repository. -->
368
368
<match>*</match>
369
-
369
+
370
+
<!--
371
+
when you run git-describe it only looks only for *annotated tags* by default
372
+
if you wish to consider *lightweight tags* in your describe as well you would need to switch this to *true*
373
+
374
+
The difference between *annotated tags* and *lightweight tags* is outlined in more depth in section [git describe and a small gotcha with tags](https://github.com/ktoso/maven-git-commit-id-plugin/#git-describe-and-a-small-gotcha-with-tags)
375
+
-->
376
+
<tags>false</tags>
377
+
370
378
<!--
371
379
always print using the "tag-commits_from_tag-g_commit_id-maybe_dirty" format, even if "on" a tag.
372
380
The distance will always be 0 if you're "on" the tag.
0 commit comments