Version 2.1.15

Version 2.1.15 is finally there and includes various bug-fixes and improvements :-)

New Features / Bug-Fixes:

The main key-aspects that have been improved or being worked on are the following:

• Introduce git.closest.tag.name and git.closest.tag.commit.count as additional output - #54
• Introduce a somewhat nasty workaround for https://issues.apache.org/jira/browse/MNG-5787 to have the plugin working with Maven 3.3.3 (#198 and #196)

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>pl.project13.maven</groupId>
    <artifactId>git-commit-id-plugin</artifactId>
    <version>2.1.15</version>
</dependency>

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Version 2.1.14

Version 2.1.14 is finally there and includes various bug-fixes and improvements :-)

Additional maintainer:

This project is currently maintained thanks to: @ktoso (founder), @TheSnoozer

New Features / Bug-Fixes:

• a git shallow clone yielded some errors when using jgit (#96)
• fixed an NPE when running plugin built under Maven 3.0.5/Java 7 under certain conditions (most likely related to docker images) - #153
• update a lot of dependencies (#161, #162, #163, #164, #165, #167, #168, #169, #172, #179)
• fixed typos in readme and other improvements (#171, #173, #187)
• introduce a demo-profile on how to use the plugin inside the pom.xml (#181)
• Introduce git.build.host as new property - #178
• Introduce includeOnlyProperties which can be used to include only certain properties into the resulting file. Please note that this configuration will be overruled by the exclude properties - #192
• Introduce build.version as new property - #192
• Plugin should use slf4j for logging - #191

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>pl.project13.maven</groupId>
    <artifactId>git-commit-id-plugin</artifactId>
    <version>2.1.14</version>
</dependency>

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Version 2.1.13

Version 2.1.13 is finally there and includes various bug-fixes and improvements :-)

New Features / Bug-Fixes:

• Using -dirty as default dirty-marker for git describe - #149
• fixed an endless build loop in Eclipse which was causes by the fact that the generated properties file was put into the source-folder and thus seemed to retrigger the eclipse build. With a new build the git-plugin updated the file with a new buildDate which then caused eclipse to detect a changed file and going into an endless cylce - #151
• Fix differences in the output of native and jgit - #155
• In previous versions the injectAllReactorProjects that was used by this plugin might have overwriten non-git properties in reactor projects. This property was previously set to true and will now be set to false.
  Please note: if you are using your git-properties inside your pom-file you need to manually set this property to true (e.g. <injectAllReactorProjects>true</injectAllReactorProjects>)

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>pl.project13.maven</groupId>
    <artifactId>git-commit-id-plugin</artifactId>
    <version>2.1.13</version>
</dependency>

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Version 2.1.12

Version 2.1.12 is finally there and includes various bug-fixes and improvements :-)

New Features / Bug-Fixes:

• Invalid defaults indicated in docs - (#52, #86, #112)
• git describe default abbrev 7 is not set by default - #134
• Allow initialization once per run (with multiple modules) with <runOnlyOnce>false</runOnlyOnce> - #53
• Extend plugin with --match option for describe - #97
• runGitDescribeWithMatchOption had trouble on Travis - #146
• Improved native git error reporting - #145
• Increase performance of dirty checking with native git - #144

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>pl.project13.maven</groupId>
    <artifactId>git-commit-id-plugin</artifactId>
    <version>2.1.12</version>
</dependency>

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Version 2.1.11

Version 2.1.11 is finally there and includes various bug-fixes and improvements :-)

New Features / Bug-Fixes:

• Extra directories created when default <generateGitPropertiesFilename> is used - #124
• Added possibility to specify encoding for generated git.properties file - currently defaults to UTF-8 - #131
• Add ability to get tag(s) for current commit - #133

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>pl.project13.maven</groupId>
    <artifactId>git-commit-id-plugin</artifactId>
    <version>2.1.11</version>
</dependency>

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Version 2.1.10

Version 2.1.10 is finally there and includes various bug-fixes and improvements :-)

New Features / Bug-Fixes:

• The plugin has now the additional option <useNativeGit>true/false</useNativeGit> option to choose whether to run with the original jgit implementation or to perform calls to the native git-binary. By default the plugin uses the jgit java implementation (<useNativeGit>false</useNativeGit>) and as a general thumb rule the native git binary should only be used if you experience any strange performance issues (e.g. git data extraction takes several minutes) or any other problems that might not be limited to git shallow clones. (#120, #119, #118, #110, #93)
• Added new property git.commit.id.short-describe that strips out commit hash and gives more (non-tech-) user friendly build number (e.g. instead of 1.2.0-123-gd3a890 it will give 1.2.0-123) - #111

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>pl.project13.maven</groupId>
    <artifactId>git-commit-id-plugin</artifactId>
    <version>2.1.10</version>
</dependency>

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Version 2.1.9

Version 2.1.9 is finally there and includes various bug-fixes and improvements :-)

New Features / Bug-Fixes:

Allows to filter which properties you want to expose (for example you might want to hide repo url, or email).

Main feature: 7c2bea0 resolves issue #91

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>pl.project13.maven</groupId>
    <artifactId>git-commit-id-plugin</artifactId>
    <version>2.1.9</version>
</dependency>

Reporting Problems

If you find any problem with this plugin, feel free to report it here