From 07c592bb4c54340f150ca0f7294323b3e2928a8b Mon Sep 17 00:00:00 2001 From: Branden Cash Date: Mon, 12 Oct 2020 19:34:51 -0700 Subject: [PATCH] v1.6.0 - added --use-yarn option --- README.md | 1 + package.json | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 521509d..011e135 100644 --- a/README.md +++ b/README.md @@ -72,6 +72,7 @@ Synchronizes the pom version to the package.json. Useful for applications that r | `--prerelease-suffix` | Suffix string to apply to the version if it is a prerelease version. If the pom version is a release version, this value is ignored. This can be useful if you want your maven build to append a build number or timestamp to the version, so each build would push up a unique version for `SNAPSHOT` versions. So if I added `--prerelease-suffix '.0'` and the pom version is something like `1.0.0-SNAPSHOT`, the resulting version would be `1.0.0-SNAPSHOT.0`. But if the pom version was `1.0.0`, the resulting version would still be `1.0.0`. | | `--pom-file` | Location of the `pom.xml` file. Defaults to use `./pom.xml` | | `--package-file` | Location of the `package.json` file. Defaults to use `./package.json` | +| `--use-yarn` | Use yarn to update version instead of npm | > Adding options in the `frontend-maven-plugin` can be done by setting the `arguments` like this: > `sync-pom-version -- --prerelease-version=.0` diff --git a/package.json b/package.json index c96178d..5c549d7 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "sync-pom-version-to-package", - "version": "1.5.0", + "version": "1.6.0", "description": "Sync's the maven project version to the package.json", "main": "index.js", "author": "Branden Cash",