vanniktech/gradle-maven-publish-plugin (com.vanniktech.maven.publish)
### [`v0.29.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0290--2024-06-20-)
[Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.28.0...0.29.0)
- Added `configureBasedOnAppliedPlugins(sourcesJar: Boolean, javadocJar: Boolean)`
overload that allows disabling sources and javadoc jars without having to use
the more granular `Platform` APIs.
- For Java library and Kotlin/JVM projects the Gradle module metadata now properly
includes the sources jar.
- When running on Gradle 8.8 or newer the pom configuration is not applied in
`afterEvaluate` anymore, making manual overrides easier.
- Fix potential issue with the javadoc jar tasks that can cause Gradle to disable
optimizations.
- When staging profiles can't be loaded the status code of the response is added
to the error message.
##### Minimum supported versions
- JDK 11
- Gradle 8.1
- Android Gradle Plugin 8.0.0
- Kotlin Gradle Plugin 1.9.20
##### Compatibility tested up to
- JDK 21
- Gradle 8.8
- Android Gradle Plugin 8.5.0
- Android Gradle Plugin 8.6.0-alpha06
- Kotlin Gradle Plugin 2.0.0
- Kotlin Gradle Plugin 2.0.20-Beta1
##### Configuration cache status
Configuration cache is generally supported, except for:
- Publishing releases to Maven Central (snapshots are fine), blocked by [Gradle issue #22779](https://togithub.com/gradle/gradle/issues/22779).
- Dokka does not support configuration cache
### [`v0.28.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0280--2024-03-12-)
[Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.27.0...0.28.0)
- Added support for publishing through the new [Central Portal](https://central.sonatype.com). To use
this use the `CENTRAL_PORTAL` option when specifying the Sonatype host.
- For Kotlin Multiplatform the main plugin will now automatically publish the
`release` variant if the project has an Android target and no variant was explicitly
specified through the Kotlin Gradle DSL.
- Support specifying the Android variants to publish in `KotlinMultiplatform(...)`.
- Updated minimum supported Gradle, Android Gradle Plugin and Kotlin versions.
- Removed support for the deprecated Kotlin/JS plugin.
- Removed the deprecated `closeAndReleaseRepository` task. Use `releaseRepository`, which
is functionally equivalent, instead.
##### Minimum supported versions
- JDK 11
- Gradle 8.1
- Android Gradle Plugin 8.0.0
- Kotlin Gradle Plugin 1.9.20
##### Compatibility tested up to
- JDK 21
- Gradle 8.6
- Gradle 8.7-rc-3
- Android Gradle Plugin 8.3.0
- Android Gradle Plugin 8.4.0-alpha13
- Kotlin Gradle Plugin 1.9.23
- Kotlin Gradle Plugin 2.0.0-Beta4
##### Configuration cache status
Configuration cache is generally supported, except for:
- Publishing releases to Maven Central (snapshots are fine), blocked by [Gradle issue #22779](https://togithub.com/gradle/gradle/issues/22779).
- Dokka does not support configuration cache
### [`v0.27.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0270--2024-01-06-)
[Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.26.0...0.27.0)
- Added new publishing related tasks
- `releaseRepository` releases a staging repository at the end of the build
and can be executed in the same build as the publishing task. This allows
having automatic releases without permanently enabling them.
- `publishToMavenCentral` as alias for running `publishAllPublicationsToMavenCentralRepository`.
- `publishAndReleaseToMavenCentral` as alias for running both of the above.
- For more information [checkout the docs](https://vanniktech.github.io/gradle-maven-publish-plugin/central/#publishing-releases).
- It is now possible to only pass a subset of the parameters to
`coordinates(...)` and leave the others at their default value.
Thanks to [@sschuberth](https://togithub.com/sschuberth) for the contribution.
- Fixed `java-test-fixture` projects being broken with Gradle 8.6.
- Deprecated `closeAndReleaseRepository` in favor of `releaseRepository`.
##### Minimum supported versions
- JDK 11
- Gradle 7.6
- Android Gradle Plugin 7.4.0
- Kotlin Gradle Plugin 1.8.20
##### Compatibility tested up to
- JDK 21
- Gradle 8.5
- Gradle 8.6-rc-1
- Android Gradle Plugin 8.2.1
- Android Gradle Plugin 8.3.0-beta01
- Android Gradle Plugin 8.4.0-alpha03
- Kotlin Gradle Plugin 1.9.22
- Kotlin Gradle Plugin 2.0.0-Beta2
##### Configuration cache status
When using **Gradle 8.1** or newer configuration cache is generally supported.
Exceptions to that are:
- Publishing releases to Maven Central (snapshots are fine), blocked by [Gradle issue #22779](https://togithub.com/gradle/gradle/issues/22779).
- Dokka does not support configuration cache
### [`v0.26.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0260--2023-12-19-)
[Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.25.3...0.26.0)
- It's now supported to call `configure(Platform)` from the main plugin to modify
what is getting published. [Check out the docs for more details](https://vanniktech.github.io/gradle-maven-publish-plugin/what/)
- The base plugin now has a `configureBasedOnAppliedPlugins` DSL method to
allow applying the default `configure` logic of the main plugin.
- Calling `configure(Platform)` now validates that the required plugins are
applied (e.g. Android Gradle Plugin for Android projects).
- It's now possible to disable source publishing for KMP projects.
- Fixed an issue which would cause the javadoc jar task to be registered multiple
times for Gradle plugin projects with more than one publication. Thanks to
[@autonomousapps](https://togithub.com/autonomousapps) for the fix.
- Publishing Kotlin/JS projects has been deprecated and will be removed in the
next release, because the Kotlin/JS plugin has been deprecated.
- The internal task to create a javadoc jar for certain project types has been renamed
from `simpleJavadocJar` to `plainJavadocJar`. Thanks to [@sschuberth](https://togithub.com/sschuberth).
##### Minimum supported versions
- JDK 11
- Gradle 7.6
- Android Gradle Plugin 7.4.0
- Kotlin Gradle Plugin 1.8.20
##### Compatibility tested up to
- JDK 21
- Gradle 8.5
- Android Gradle Plugin 8.2.0
- Android Gradle Plugin 8.3.0-alpha17
- Kotlin Gradle Plugin 1.9.21
- Kotlin Gradle Plugin 2.0.0-Beta1
##### Configuration cache status
When using **Gradle 8.1** or newer configuration cache is generally supported.
Exceptions to that are:
- Publishing releases to Maven Central (snapshots are fine), blocked by [Gradle issue #22779](https://togithub.com/gradle/gradle/issues/22779).
- Dokka does not support configuration cache
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 contains the following updates:
0.25.3->0.29.0Release Notes
vanniktech/gradle-maven-publish-plugin (com.vanniktech.maven.publish)
### [`v0.29.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0290--2024-06-20-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.28.0...0.29.0) - Added `configureBasedOnAppliedPlugins(sourcesJar: Boolean, javadocJar: Boolean)` overload that allows disabling sources and javadoc jars without having to use the more granular `Platform` APIs. - For Java library and Kotlin/JVM projects the Gradle module metadata now properly includes the sources jar. - When running on Gradle 8.8 or newer the pom configuration is not applied in `afterEvaluate` anymore, making manual overrides easier. - Fix potential issue with the javadoc jar tasks that can cause Gradle to disable optimizations. - When staging profiles can't be loaded the status code of the response is added to the error message. ##### Minimum supported versions - JDK 11 - Gradle 8.1 - Android Gradle Plugin 8.0.0 - Kotlin Gradle Plugin 1.9.20 ##### Compatibility tested up to - JDK 21 - Gradle 8.8 - Android Gradle Plugin 8.5.0 - Android Gradle Plugin 8.6.0-alpha06 - Kotlin Gradle Plugin 2.0.0 - Kotlin Gradle Plugin 2.0.20-Beta1 ##### Configuration cache status Configuration cache is generally supported, except for: - Publishing releases to Maven Central (snapshots are fine), blocked by [Gradle issue #22779](https://togithub.com/gradle/gradle/issues/22779). - Dokka does not support configuration cache ### [`v0.28.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0280--2024-03-12-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.27.0...0.28.0) - Added support for publishing through the new [Central Portal](https://central.sonatype.com). To use this use the `CENTRAL_PORTAL` option when specifying the Sonatype host. - For Kotlin Multiplatform the main plugin will now automatically publish the `release` variant if the project has an Android target and no variant was explicitly specified through the Kotlin Gradle DSL. - Support specifying the Android variants to publish in `KotlinMultiplatform(...)`. - Updated minimum supported Gradle, Android Gradle Plugin and Kotlin versions. - Removed support for the deprecated Kotlin/JS plugin. - Removed the deprecated `closeAndReleaseRepository` task. Use `releaseRepository`, which is functionally equivalent, instead. ##### Minimum supported versions - JDK 11 - Gradle 8.1 - Android Gradle Plugin 8.0.0 - Kotlin Gradle Plugin 1.9.20 ##### Compatibility tested up to - JDK 21 - Gradle 8.6 - Gradle 8.7-rc-3 - Android Gradle Plugin 8.3.0 - Android Gradle Plugin 8.4.0-alpha13 - Kotlin Gradle Plugin 1.9.23 - Kotlin Gradle Plugin 2.0.0-Beta4 ##### Configuration cache status Configuration cache is generally supported, except for: - Publishing releases to Maven Central (snapshots are fine), blocked by [Gradle issue #22779](https://togithub.com/gradle/gradle/issues/22779). - Dokka does not support configuration cache ### [`v0.27.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0270--2024-01-06-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.26.0...0.27.0) - Added new publishing related tasks - `releaseRepository` releases a staging repository at the end of the build and can be executed in the same build as the publishing task. This allows having automatic releases without permanently enabling them. - `publishToMavenCentral` as alias for running `publishAllPublicationsToMavenCentralRepository`. - `publishAndReleaseToMavenCentral` as alias for running both of the above. - For more information [checkout the docs](https://vanniktech.github.io/gradle-maven-publish-plugin/central/#publishing-releases). - It is now possible to only pass a subset of the parameters to `coordinates(...)` and leave the others at their default value. Thanks to [@sschuberth](https://togithub.com/sschuberth) for the contribution. - Fixed `java-test-fixture` projects being broken with Gradle 8.6. - Deprecated `closeAndReleaseRepository` in favor of `releaseRepository`. ##### Minimum supported versions - JDK 11 - Gradle 7.6 - Android Gradle Plugin 7.4.0 - Kotlin Gradle Plugin 1.8.20 ##### Compatibility tested up to - JDK 21 - Gradle 8.5 - Gradle 8.6-rc-1 - Android Gradle Plugin 8.2.1 - Android Gradle Plugin 8.3.0-beta01 - Android Gradle Plugin 8.4.0-alpha03 - Kotlin Gradle Plugin 1.9.22 - Kotlin Gradle Plugin 2.0.0-Beta2 ##### Configuration cache status When using **Gradle 8.1** or newer configuration cache is generally supported. Exceptions to that are: - Publishing releases to Maven Central (snapshots are fine), blocked by [Gradle issue #22779](https://togithub.com/gradle/gradle/issues/22779). - Dokka does not support configuration cache ### [`v0.26.0`](https://togithub.com/vanniktech/gradle-maven-publish-plugin/blob/HEAD/CHANGELOG.md#0260--2023-12-19-) [Compare Source](https://togithub.com/vanniktech/gradle-maven-publish-plugin/compare/0.25.3...0.26.0) - It's now supported to call `configure(Platform)` from the main plugin to modify what is getting published. [Check out the docs for more details](https://vanniktech.github.io/gradle-maven-publish-plugin/what/) - The base plugin now has a `configureBasedOnAppliedPlugins` DSL method to allow applying the default `configure` logic of the main plugin. - Calling `configure(Platform)` now validates that the required plugins are applied (e.g. Android Gradle Plugin for Android projects). - It's now possible to disable source publishing for KMP projects. - Fixed an issue which would cause the javadoc jar task to be registered multiple times for Gradle plugin projects with more than one publication. Thanks to [@autonomousapps](https://togithub.com/autonomousapps) for the fix. - Publishing Kotlin/JS projects has been deprecated and will be removed in the next release, because the Kotlin/JS plugin has been deprecated. - The internal task to create a javadoc jar for certain project types has been renamed from `simpleJavadocJar` to `plainJavadocJar`. Thanks to [@sschuberth](https://togithub.com/sschuberth). ##### Minimum supported versions - JDK 11 - Gradle 7.6 - Android Gradle Plugin 7.4.0 - Kotlin Gradle Plugin 1.8.20 ##### Compatibility tested up to - JDK 21 - Gradle 8.5 - Android Gradle Plugin 8.2.0 - Android Gradle Plugin 8.3.0-alpha17 - Kotlin Gradle Plugin 1.9.21 - Kotlin Gradle Plugin 2.0.0-Beta1 ##### Configuration cache status When using **Gradle 8.1** or newer configuration cache is generally supported. Exceptions to that are: - Publishing releases to Maven Central (snapshots are fine), blocked by [Gradle issue #22779](https://togithub.com/gradle/gradle/issues/22779). - Dokka does not support configuration cacheConfiguration
📅 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 was generated by Mend Renovate. View the repository job log.