|
4 | 4 | <groupId>org.apache.hadoop.fs.glusterfs</groupId>
|
5 | 5 | <artifactId>glusterfs</artifactId>
|
6 | 6 | <packaging>jar</packaging>
|
7 |
| - <version>0.0.1-${maven.build.timestamp}</version> |
| 7 | + <version>snapshot-${maven.build.timestamp}</version> |
8 | 8 | <name>glusterfs</name>
|
9 | 9 | <url>http://maven.apache.org</url>
|
10 | 10 | <dependencies>
|
|
82 | 82 | <target>1.5</target>
|
83 | 83 | </configuration>
|
84 | 84 | </plugin>
|
85 |
| - |
| 85 | + |
| 86 | +<plugin> |
| 87 | + <groupId>pl.project13.maven</groupId> |
| 88 | + <artifactId>git-commit-id-plugin</artifactId> |
| 89 | + <version>2.1.4</version> |
| 90 | + <executions> |
| 91 | + <execution> |
| 92 | + <goals> |
| 93 | + <goal>revision</goal> |
| 94 | + </goals> |
| 95 | + </execution> |
| 96 | + </executions> |
| 97 | + |
| 98 | + <configuration> |
| 99 | + <!-- that's the default value, you don't have to set it --> |
| 100 | + <prefix>git</prefix> |
| 101 | + |
| 102 | + <!-- that's the default value --> |
| 103 | + <dateFormat>dd.MM.yyyy '@' HH:mm:ss z</dateFormat> |
| 104 | + |
| 105 | + <!-- true is default here, it prints some more information during the build --> |
| 106 | + <verbose>true</verbose> |
| 107 | + |
| 108 | + <!-- |
| 109 | + If you'd like to tell the plugin where your .git directory is, |
| 110 | + use this setting, otherwise we'll perform a search trying to |
| 111 | + figure out the right directory. It's better to add it explicite IMHO. |
| 112 | + --> |
| 113 | + <dotGitDirectory>${project.basedir}/.git</dotGitDirectory> |
| 114 | + |
| 115 | + <!-- ALTERNATE SETUP - GENERATE FILE --> |
| 116 | + <!-- |
| 117 | + If you want to keep git information, even in your WAR file etc, |
| 118 | + use this mode, which will generate a properties file (with filled out values) |
| 119 | + which you can then normally read using new Properties().load(/**/) |
| 120 | + --> |
| 121 | + |
| 122 | + <!-- |
| 123 | + this is true by default; You may want to set this to false, if the plugin should run inside a |
| 124 | + <packaging>pom</packaging> project. Most projects won't need to override this property. |
| 125 | +
|
| 126 | + For an use-case for this kind of behaviour see: https://github.com/ktoso/maven-git-commit-id-plugin/issues/21 |
| 127 | + --> |
| 128 | + <skipPoms>true</skipPoms> |
| 129 | + |
| 130 | + <!-- this is false by default, forces the plugin to generate the git.properties file --> |
| 131 | + <generateGitPropertiesFile>true</generateGitPropertiesFile> |
| 132 | + |
| 133 | + <!-- The path for the to be generated properties file, it's relative to ${project.basedir} --> |
| 134 | + <generateGitPropertiesFilename>src/main/resources/git.properties</generateGitPropertiesFilename> |
| 135 | + |
| 136 | + <!-- true by default, controls whether the plugin will fail when no .git directory is found, when set to false the plugin will just skip execution --> |
| 137 | + <!-- @since 2.0.4 --> |
| 138 | + <failOnNoGitDirectory>false</failOnNoGitDirectory> |
| 139 | + |
| 140 | + <!-- @since 2.1.0 --> |
| 141 | + <!-- |
| 142 | + read up about git-describe on the in man, or it's homepage - it's a really powerful versioning helper |
| 143 | + and the recommended way to use git-commit-id-plugin. The configuration bellow is optional, |
| 144 | + by default describe will run "just like git-describe on the command line", even though it's a JGit reimplementation. |
| 145 | + --> |
| 146 | + <gitDescribe> |
| 147 | + |
| 148 | + <!-- don't generate the describe property --> |
| 149 | + <skip>false</skip> |
| 150 | + |
| 151 | + <!-- |
| 152 | + if no tag was found "near" this commit, just print the commit's id instead, |
| 153 | + helpful when you always expect this field to be not-empty |
| 154 | + --> |
| 155 | + <always>false</always> |
| 156 | + <!-- |
| 157 | + how many chars should be displayed as the commit object id? |
| 158 | + 7 is git's default, |
| 159 | + 0 has a special meaning (see end of this README.md), |
| 160 | + and 40 is the maximum value here |
| 161 | + --> |
| 162 | + <abbrev>7</abbrev> |
| 163 | + |
| 164 | + <!-- when the build is triggered while the repo is in "dirty state", append this suffix --> |
| 165 | + <dirty>-dirty</dirty> |
| 166 | + |
| 167 | + <!-- |
| 168 | + always print using the "tag-commits_from_tag-g_commit_id-maybe_dirty" format, even if "on" a tag. |
| 169 | + The distance will always be 0 if you're "on" the tag. |
| 170 | + --> |
| 171 | + <forceLongFormat>false</forceLongFormat> |
| 172 | + </gitDescribe> |
| 173 | + </configuration> |
| 174 | + |
| 175 | + </plugin> |
86 | 176 |
|
87 | 177 | </plugins>
|
88 | 178 | </build>
|
|
0 commit comments