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: CHANGELOG.md
+34Lines changed: 34 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,39 @@
1
1
# Changelog
2
2
3
+
## v1.17.0 (2021-12-07)
4
+
5
+
* Fixed and improved error messages in `feature-start` goal - [#306](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/306)
6
+
* Added ability to use different commit message on feature squash - [#287](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/287)
7
+
* Added ability to increment different digit in hotfix version - [#186](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/186)
8
+
* Added ability to disable update of `project.build.outputTimestamp` property - [#310](https://github.com/aleksandr-m/gitflow-maven-plugin/pull/310)
9
+
* Added support to automatically use Maven wrapper for internal commands - [#246](https://github.com/aleksandr-m/gitflow-maven-plugin/pull/246)
10
+
* Added ability to use `gitFlowConfig` and `commitMessages` properties from the command line - [#284](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/284)
11
+
12
+
## v1.16.0 (2021-03-23)
13
+
14
+
* Fixed wrong incrementing of feature name - [#288](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/288)
15
+
* Fixed wrong version property update - [#272](https://github.com/aleksandr-m/gitflow-maven-plugin/pull/272)
16
+
* Added support for updating `project.build.outputTimestamp` property to support [Maven reproducible builds](https://maven.apache.org/guides/mini/guide-reproducible-builds.html) - [#286](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/286)
17
+
* Removed deprecated wrong spelling of commit message parameter
18
+
* Added ability to use snapshot version in support branch - [#250](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/250)
19
+
* Added ability to change support branch name - [#276](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/276)
20
+
* Added ability to use full branch name in feature and hotfix finish goals - [#270](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/270)
21
+
22
+
## v1.15.1 (2021-01-14)
23
+
24
+
* Fixed `hotfix-finish` must not increment develop snapshot version [#267](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/267)
25
+
26
+
## v1.15.0 (2020-11-04)
27
+
28
+
* Updated java version to 1.7 - [#252](https://github.com/aleksandr-m/gitflow-maven-plugin/pull/252)
29
+
* Changed commit logic in `feature-finish` goal to avoid directly committing into the develop - [#226](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/226)
30
+
* Fixed wrong development version after `hotfix-finish` - [#211](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/211)
31
+
* Fixed failing `hotfix-finish` in fresh checkout - [#219](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/219)
32
+
* Added ability to skip merging release into production branch - [#74](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/74)
33
+
* Added ability to increment feature version during `feature-finish` goal - [#162](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/162)
34
+
* Added current feature branch as the default choice for `feature-finish` - [#227](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/227)
35
+
* Added properties to `featureFinishDevMergeMessage` message - [#247](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/247)
36
+
3
37
## v1.14.0 (2019-12-06)
4
38
5
39
* Fixed snapshot dependencies check and improved version resolution - [#204](https://github.com/aleksandr-m/gitflow-maven-plugin/pull/204)
@@ -22,7 +23,7 @@ The plugin is available from Maven Central.
22
23
<plugin>
23
24
<groupId>com.amashchenko.maven.plugin</groupId>
24
25
<artifactId>gitflow-maven-plugin</artifactId>
25
-
<version>1.14.0</version>
26
+
<version>1.17.0</version>
26
27
<configuration>
27
28
<!-- optional configuration -->
28
29
</configuration>
@@ -60,6 +61,9 @@ To configure this plugin to use single branch model, such as GitHub Flow, just s
60
61
61
62
That's it!
62
63
64
+
# Maven Wrapper support
65
+
66
+
The plugin will automatically use Maven Wrapper for internal Maven goals if plugin is started with the wrapper.
63
67
64
68
# Eclipse Plugins build with Tycho
65
69
@@ -100,6 +104,17 @@ The `gitflow:release`, `gitflow:release-finish` and `gitflow:hotfix-finish` goal
100
104
All goals have `gpgSignCommit` parameter. Set it to `true` to sign commits with configured personal key. The default value is `false`.
101
105
102
106
107
+
# Support for Reproducible Builds
108
+
109
+
[Reproducible builds](https://reproducible-builds.org/) are a set of software development practices that create an independently-verifiable path from source to binary code.
110
+
111
+
To configure your Maven build to support reproducible builds follow [official guide](https://maven.apache.org/guides/mini/guide-reproducible-builds.html).
112
+
113
+
If your project has `project.build.outputTimestamp` property this plugin will update its value whenever the versions are updated.
114
+
115
+
This can be disabled by setting the configuration parameter `updateOutputTimestamp` to `false`.
116
+
117
+
103
118
# Plugin Common Parameters
104
119
105
120
All parameters are optional. The `gitFlowConfig` parameters defaults are the same as in the example below.
@@ -156,6 +171,7 @@ Since `1.2.1` commit messages can be changed in plugin's configuration section i
@@ -181,7 +197,7 @@ Maven properties can be used in commit messages. For example `<featureStartMessa
181
197
182
198
Note that although `${project.version}` can be used, any changes to version introduced by this goal won't be reflected in a commit message for this goal (see Custom properties).
183
199
184
-
Commit messages can be prefixed by using `commitMessagePrefix` parameter.
200
+
Commit messages can be prefixed by using `commitMessagePrefix` parameter. Leading or trailing whitespaces can be preserved by using `xml:space="preserve"` attribute e.g. `<commitMessagePrefix xml:space="preserve">[gitflow] </commitMessagePrefix>`.
185
201
186
202
### Custom properties in commit messages
187
203
@@ -201,8 +217,7 @@ For example, `-DversionProperty=revision` will update the `<revision>` property
201
217
202
218
The `skipUpdateVersion` parameter can be used to skip updating `<version>` in the pom.xml. The default value is `false` (i.e. the version will be updated).
203
219
204
-
To support [CI friendly versioning](https://maven.apache.org/maven-ci-friendly.html) in projects which use `<version>${revision}</version>` (e.g. [spring-boot](https://github.com/spring-projects/spring-boot/blob/master/pom.xml))
205
-
set `versionProperty` to `revision` and `skipUpdateVersion` to `true`.
220
+
To support [CI friendly versioning](https://maven.apache.org/maven-ci-friendly.html) in projects which use `<version>${revision}</version>` set `versionProperty` to `revision` and `skipUpdateVersion` to `true`.
206
221
207
222
## Additional goal parameters
208
223
@@ -215,6 +230,8 @@ The default value is `false` (e.g. if the project version is `1.0.0-SNAPSHOT` an
215
230
The `gitflow:feature-start` goal has `featureNamePattern` parameter which allows to enforce naming of the feature branches with a regular expression. Doesn't have effect if it isn't set or left blank.
216
231
By default it isn't set.
217
232
233
+
The `gitflow:feature-finish` goal has `incrementVersionAtFinish` parameter which if set to `true` will increment version number during feature finish. The default is `false`.
234
+
218
235
All `-finish` goals have `keepBranch` parameter which controls whether created support branch will be kept in Git after the goal finishes.
219
236
The default value is `false` (i.e. the supporting branch will be deleted). If the `pushRemote` parameter is set to `true` and `keepBranch` is `false` remote branch will be deleted as well.
220
237
@@ -250,12 +267,16 @@ The `gitflow:release-start` goal has `fromCommit` parameter which allows to star
250
267
The `gitflow:release-start` and `gitflow:release-finish` goals have `useSnapshotInRelease` parameter which allows to start the release with SNAPSHOT version and finish it without this value in project version. By default the value is `false`.
251
268
For example, if the release version is `1.0.2` and `useSnapshotInRelease` is set to `true` and using `gitflow:release-start` goal then the release version will be `1.0.2-SNAPSHOT` and when finishing the release with `gitflow:release-finish` goal, the release version will be `1.0.2`
252
269
270
+
The `gitflow:release` and `gitflow:release-start` goals have `skipReleaseMergeProdBranch` parameter which prevents merging the release branch into the production branch. The default value is `false`.
271
+
253
272
The `gitflow:hotfix-start` and `gitflow:hotfix-finish` goals have `useSnapshotInHotfix` parameter which allows to start the hotfix with SNAPSHOT version and finish it without this value in the version. By default the value is `false`.
254
273
For example, if the hotfix version is `1.0.2.1` and `useSnapshotInHotfix` is set to `true` and using `gitflow:hotfix-start` goal then the hotfix version will be `1.0.2.1-SNAPSHOT` and when finishing the release with `gitflow:hotfix-finish` goal, the release version will be `1.0.2.1`
255
274
256
-
The `gitflow:hotfix-finish` goal also supports the parameter `skipMergeDevBranch` which prevents merging the hotfix branch into the development branch.
275
+
The `gitflow:hotfix-finish` goal supports the parameter `skipMergeDevBranch` which prevents merging the hotfix branch into the development branch.
257
276
258
-
The `gitflow:hotfix-finish` goal also supports the parameter `skipMergeProdBranch` which prevents merging the hotfix branch into the production branch and deletes the hotfix branch leaving only the tagged commit. Useful, along with `skipMergeDevBranch`, to allow hotfixes to very old code that are not applicable to current development.
277
+
The `gitflow:hotfix-finish` goal supports the parameter `skipMergeProdBranch` which prevents merging the hotfix branch into the production branch and deletes the hotfix branch leaving only the tagged commit. Useful, along with `skipMergeDevBranch`, to allow hotfixes to very old code that are not applicable to current development.
278
+
279
+
The `gitflow:hotfix-start` goal has `hotfixVersionDigitToIncrement` parameter which controls which digit to increment in the hotfix version. Starts from zero.
259
280
260
281
Version update of all modules ignoring groupId and artifactId can be forced by setting `versionsForceUpdate` parameter to `true`. The default value is `false`.
261
282
@@ -321,6 +342,8 @@ The `gitflow:release-finish` and `gitflow:release` goals have `developmentVersio
321
342
322
343
The `gitflow:feature-start` and `gitflow:feature-finish` goals have `featureName` parameter which can be used to set a name of the feature in non-interactive mode.
323
344
345
+
The `gitflow:feature-finish` goal has `featureBranch` parameter which can be used to set feature branch name in non-interactive mode. It must start with the feature branch prefix. The `featureBranch` will be used instead of `featureName` if both are set.
346
+
324
347
## Non-interactive Hotfix
325
348
326
349
The `gitflow:hotfix-start` goal has `fromBranch` parameter which can be used to set starting branch of the hotfix. It can be set to production branch or one of the support branches.
@@ -329,7 +352,13 @@ If it is left blank then hotfix will be started from the production branch.
329
352
The `gitflow:hotfix-start` and `gitflow:hotfix-finish` goals have `hotfixVersion` parameter which can be used to set version of the hotfix.
330
353
If it is left blank in `gitflow:hotfix-start` goal then the default version will be used.
331
354
355
+
The `gitflow:hotfix-finish` goal has `hotfixBranch` parameter which can be used to set hotfix branch name in non-interactive mode. It must start with the hotfix branch prefix. The `hotfixBranch` will be used instead of `hotfixVersion` if both are set.
356
+
332
357
## Non-interactive Support
333
358
334
359
The `gitflow:support-start` goal can be run in non-interactive mode. Use `tagName` parameter to set tag from which supporting branch will be started.
335
360
If `tagName` is not set but the goal is running in non-interactive mode then the last tag will be used.
361
+
362
+
The `gitflow:support-start` goal has `supportBranchName` parameter which can be used to set branch name to use instead of the default.
363
+
364
+
The `gitflow:support-start` goal has `useSnapshotInSupport` parameter which allows to start the support with SNAPSHOT version.
0 commit comments