vanniktech/gradle-maven-publish-plugin
### [`v0.23.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#Version-0230--2022-12-29-)
[Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.22.0...0.23.0)
Updated docs can be found on [the new website](https://vanniktech.github.io/gradle-maven-publish-plugin/).
- **NEW**: It is now possible to set group id, artifact id directly through the DSL
```groovy
mavenPublishing {
coordinates("com.example", "library", "1.0.3")
}
```
- `project.group` and `project.version` will still be used as default values for group and version if the
`GROUP`/`VERSION_NAME` Gradle properties do not exist and `coordinates` was not called, however there are 2
**behavior changes**:
- The `GROUP` and `VERSION_NAME` Gradle properties take precedence over `project.group` and `project.version` instead
of being overwritten by them. If you need to define the properties but replace them for some projects,
please use the new `coordinates` method instead.
- The `GROUP` and `VERSION_NAME` Gradle properties will not be explicitly set as `project.group` and
`project.version` anymore.
- **NEW**: Added `dropRepository` task that will drop a Sonatype staging repository. It is possible to specify
which repository to drop by adding a `--repository` parameter with the id of the staging repository that was
printed during `publish`. If no repository is specified and there is only one staging repository, that one
will be dropped.
- Added workaround to also publish sources for the `java-test-fixtures` plugin
- Fixed publishing Kotlin/JS projects with the base plugin.
- Fixed that a POM configured through the DSL is incomplete when publishing Gradle plugins.
- The minimum supported Gradle version has been increased to 7.3.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
0.22.0->0.23.0Release Notes
vanniktech/gradle-maven-publish-plugin
### [`v0.23.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#Version-0230--2022-12-29-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.22.0...0.23.0) Updated docs can be found on [the new website](https://vanniktech.github.io/gradle-maven-publish-plugin/). - **NEW**: It is now possible to set group id, artifact id directly through the DSL ```groovy mavenPublishing { coordinates("com.example", "library", "1.0.3") } ``` - `project.group` and `project.version` will still be used as default values for group and version if the `GROUP`/`VERSION_NAME` Gradle properties do not exist and `coordinates` was not called, however there are 2 **behavior changes**: - The `GROUP` and `VERSION_NAME` Gradle properties take precedence over `project.group` and `project.version` instead of being overwritten by them. If you need to define the properties but replace them for some projects, please use the new `coordinates` method instead. - The `GROUP` and `VERSION_NAME` Gradle properties will not be explicitly set as `project.group` and `project.version` anymore. - **NEW**: Added `dropRepository` task that will drop a Sonatype staging repository. It is possible to specify which repository to drop by adding a `--repository` parameter with the id of the staging repository that was printed during `publish`. If no repository is specified and there is only one staging repository, that one will be dropped. - Added workaround to also publish sources for the `java-test-fixtures` plugin - Fixed publishing Kotlin/JS projects with the base plugin. - Fixed that a POM configured through the DSL is incomplete when publishing Gradle plugins. - The minimum supported Gradle version has been increased to 7.3.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.