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
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,22 @@
1
1
# Changelog
2
2
3
+
## v1.18.0 (2022-02-20)
4
+
5
+
### Breaking changes
6
+
7
+
* Changed default branch to merge during release. Now tag or production branch will be merged to development branch. To restore previous behavior and merge release branch use `noBackMerge` parameter - [#213](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/213)
8
+
* Changed default branch to merger during hotfix. Now tag or production branch will be merged to development branch. To restore previous behavior and merge hotfix branch use `noBackMergeHotfix` parameter - [#328](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/328)
9
+
* Changed default versions of internal plugins `versions-maven-plugin` and `tycho-versions-plugin`. Now it is set in the code and can be modified with properties - [#330](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/330)
10
+
11
+
### ---
12
+
13
+
* Added new `version-update` goal - [#269](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/269)
14
+
* Improved getting current version of the project - [#324](https://github.com/aleksandr-m/gitflow-maven-plugin/pull/324)
15
+
* Added check for SNAPSHOT dependency in parent project definition - [#64](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/64)
16
+
* Added ability to use [Maven version policy](https://maven.apache.org/maven-release/maven-release-api/apidocs/org/apache/maven/shared/release/policy/version/VersionPolicy.html) - [#235](https://github.com/aleksandr-m/gitflow-maven-plugin/pull/236)
17
+
* Added checkout from remote for development branch in `feature-start` goal - [#322](https://github.com/aleksandr-m/gitflow-maven-plugin/pull/322)
18
+
* Added ability to add [push-options](https://git-scm.com/docs/git-push#Documentation/git-push.txt--oltoptiongt) to git push - [#319](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/319)
19
+
3
20
## v1.17.0 (2021-12-07)
4
21
5
22
* Fixed and improved error messages in `feature-start` goal - [#306](https://github.com/aleksandr-m/gitflow-maven-plugin/issues/306)
Copy file name to clipboardExpand all lines: README.md
+33-9Lines changed: 33 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ The plugin is available from Maven Central.
23
23
<plugin>
24
24
<groupId>com.amashchenko.maven.plugin</groupId>
25
25
<artifactId>gitflow-maven-plugin</artifactId>
26
-
<version>1.17.0</version>
26
+
<version>1.18.0</version>
27
27
<configuration>
28
28
<!-- optional configuration -->
29
29
</configuration>
@@ -42,6 +42,7 @@ The plugin is available from Maven Central.
42
42
-`gitflow:hotfix-start` - Starts a hotfix branch and updates version(s) to hotfix version.
43
43
-`gitflow:hotfix-finish` - Merges a hotfix branch.
44
44
-`gitflow:support-start` - Starts a support branch from the production tag.
45
+
-`gitflow:version-update` - Updates version in release or support branch, optionally tagging and pushing it to the remote repository.
45
46
-`gitflow:help` - Displays help information.
46
47
47
48
@@ -61,10 +62,17 @@ To configure this plugin to use single branch model, such as GitHub Flow, just s
61
62
62
63
That's it!
63
64
65
+
64
66
# Maven Wrapper support
65
67
66
68
The plugin will automatically use Maven Wrapper for internal Maven goals if plugin is started with the wrapper.
67
69
70
+
71
+
# Internal Maven plugins
72
+
73
+
The `versions-maven-plugin` and `tycho-versions-plugin` are used internally to update versions and properties of the project. To change versions of internal plugins use `versionsMavenPluginVersion` and `tychoVersionsPluginVersion` properties respectively.
74
+
75
+
68
76
# Eclipse Plugins build with Tycho
69
77
70
78
Since version `1.1.0` this plugin supports Eclipse plugin projects which are build with [Tycho](https://eclipse.org/tycho/).
@@ -182,13 +190,21 @@ Since `1.2.1` commit messages can be changed in plugin's configuration section i
<tagVersionUpdateMessage>Tag version update</tagVersionUpdateMessage>
185
194
186
195
<!-- Migration Note: This was called <updateDevToAvoidConflitsMessage> in version 1.11.0, but has been deprecated in favour of the correctly spelt one below. -->
187
196
<updateDevToAvoidConflictsMessage>Update develop to production version to avoid merge conflicts</updateDevToAvoidConflictsMessage>
188
197
<updateDevBackPreMergeStateMessage>Update develop version back to pre-merge state</updateDevBackPreMergeStateMessage>
189
198
190
199
<updateReleaseToAvoidConflictsMessage>Update release to hotfix version to avoid merge conflicts</updateReleaseToAvoidConflictsMessage>
191
200
<updateReleaseBackPreMergeStateMessage>Update release version back to pre-merge state</updateReleaseBackPreMergeStateMessage>
201
+
202
+
<updateFeatureBackMessage>Update feature branch back to feature version</updateFeatureBackMessage>
@@ -240,14 +256,6 @@ The default value is `false` (i.e. the project will be tested before merging bra
240
256
241
257
All `release` goals have `allowSnapshots` parameter which controls whether SNAPSHOT dependencies are allowed. The default value is `false` (i.e. build fails if there SNAPSHOT dependency in project).
242
258
243
-
The `gitflow:release-finish` and `gitflow:release` goals have `digitsOnlyDevVersion` parameter which will remove qualifiers from the next development version if set to `true`.
244
-
For example, if the release version is `1.0.0-Final` then development version will be `1.0.1-SNAPSHOT`.
245
-
The default value is `false` (i.e. qualifiers will be preserved in next development version).
246
-
247
-
The `gitflow:release-finish` and `gitflow:release` goals have `versionDigitToIncrement` parameter which controls which digit to increment in the next development version. Starts from zero.
248
-
For example, if the release version is `1.2.3.4` and `versionDigitToIncrement` is set to `1` then the next development version will be `1.3.0.0-SNAPSHOT`.
249
-
If not set or set to not valid value defaults to increment last digit in the version.
250
-
251
259
The `gitflow:release-start` and `gitflow:release-finish` have `commitDevelopmentVersionAtStart` parameter which controls whether the next development version is set and committed at start or after finish.
252
260
By default the value is `false` which means that the next development version is set on the development branch after the release branch has been merged onto the development branch when finishing the release.
253
261
This has the benefit of being able to easily cancel the release process simply by deleting the release branch.
@@ -276,8 +284,22 @@ The `gitflow:hotfix-finish` goal supports the parameter `skipMergeDevBranch` whi
276
284
277
285
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
286
287
+
The `gitflow:release-finish` and `gitflow:hofix-finish` goals have `noBackMerge` and `noBackMergeHotfix` parameters respectively. They control which branch is merged to development branch. If set to `true` then release or hotfix branch will be merged to development branch. If set to `false` and tag is present (`skipTag` parameter is set to `false`) then tag will be merged. If there is no tag then production branch will be merged to development branch.
288
+
289
+
### Versioning
290
+
291
+
The `gitflow:release-finish` and `gitflow:release` goals have `digitsOnlyDevVersion` parameter which will remove qualifiers from the next development version if set to `true`.
292
+
For example, if the release version is `1.0.0-Final` then development version will be `1.0.1-SNAPSHOT`.
293
+
The default value is `false` (i.e. qualifiers will be preserved in next development version).
294
+
295
+
The `gitflow:release-finish` and `gitflow:release` goals have `versionDigitToIncrement` parameter which controls which digit to increment in the next development version. Starts from zero.
296
+
For example, if the release version is `1.2.3.4` and `versionDigitToIncrement` is set to `1` then the next development version will be `1.3.0.0-SNAPSHOT`.
297
+
If not set or set to not valid value defaults to increment last digit in the version.
298
+
279
299
The `gitflow:hotfix-start` goal has `hotfixVersionDigitToIncrement` parameter which controls which digit to increment in the hotfix version. Starts from zero.
280
300
301
+
Versioninig can be controlled by using [Maven version policy](https://maven.apache.org/maven-release/maven-release-api/apidocs/org/apache/maven/shared/release/policy/version/VersionPolicy.html) implementation. Create appropriate implementation and add it as dependency to the project, use `projectVersionPolicyId` parameter to set policy id to use. If policy is set then other parameters controlling the generation of version are ignored (i.e. `digitsOnlyDevVersion`, `versionDigitToIncrement`).
302
+
281
303
Version update of all modules ignoring groupId and artifactId can be forced by setting `versionsForceUpdate` parameter to `true`. The default value is `false`.
282
304
283
305
### Remote interaction
@@ -291,6 +313,8 @@ At the end of the `-start` goals newly created branch (release / feature / hotfi
291
313
292
314
The default remote name is `origin`. It can be customized with `<gitFlowConfig><origin>custom_origin</origin></gitFlowConfig>` configuration in pom.xml.
293
315
316
+
Git [push-options](https://git-scm.com/docs/git-push#Documentation/git-push.txt--oltoptiongt) can be added to push command with the `gitPushOptions` parameter. Multiple options can be added separated with a space e.g. `-DgitPushOptions="merge_request.create merge_request.target=develop merge_request.label='Super feature'"`.
317
+
294
318
### Rebase, Merge, Fast Forward, Squash
295
319
296
320
Release branch can be rebased instead of merged by setting `releaseRebase` parameter to `true`. The default value is `false` (i.e. merge will be performed).
Copy file name to clipboardExpand all lines: pom.xml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@
21
21
<artifactId>gitflow-maven-plugin</artifactId>
22
22
<packaging>maven-plugin</packaging>
23
23
<name>gitflow-maven-plugin</name>
24
-
<version>1.17.1-SNAPSHOT</version>
24
+
<version>1.18.0</version>
25
25
26
26
<description>The Git-Flow Maven Plugin supports various Git workflows, including Vincent Driessen's successful Git branching model and GitHub Flow. This plugin runs Git and Maven commands from the command line. Supports Eclipse Plugins build with Tycho.</description>
0 commit comments