vanniktech/gradle-maven-publish-plugin (com.vanniktech:gradle-maven-publish-plugin)
### [`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
Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), 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.28.0->0.29.0Release Notes
vanniktech/gradle-maven-publish-plugin (com.vanniktech:gradle-maven-publish-plugin)
### [`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 cacheConfiguration
📅 Schedule: Branch creation - "every weekend" (UTC), 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.