common-gradle-dependencies v0.9.0-20241203 release #22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…on` to the release version
…hot in the `sonatype-ossrh-publish` plugin Somehow with the original approach of configuring `onlyIf` in the `Sign` tasks, when the signing key is configured in `~/.gradle/gradle.properties`, `publishToMavenLocal` becomes significantly slower. This solves the problem. Bump the aligned project version BTW.
…adapted from "kotlin-common" A source commit: huanshankeji/kotlin-common@157159b The `dokkaGenerate` tasks fails with the following error: ```text Execution failed for task ':dokkaGeneratePublicationHtml'. > Could not resolve all files for configuration ':dokkaHtmlPluginIntransitiveResolver~internal'. > Cannot resolve external dependency org.jetbrains.dokka:templating-plugin:2.0.0-Beta because no repositories are defined. Required by: root project : > Cannot resolve external dependency org.jetbrains.dokka:dokka-base:2.0.0-Beta because no repositories are defined. Required by: root project : ``` This may be a bug from Dokka. See Kotlin/dokka#2260.
Deploy the API documentation to GitHub Pages with Dokka
… and the build code
Changes: 1. use the project relative path in the source remote URL to improve its versatility 1. fix the bug that incorrect release tags `v...`` are used, while correct ones should be `plugins-v...` 1. put the `dokka` configuration code in `afterEvaluate` so the project version can be retrieved
…ctories while "blob" is for files You get redirected if using the wrong one though.
…adle.api.internal.provider.MissingValueException` in projects in the Dokka convention plugins
…lve an additional error
While running `dokkaGenerate` in dependent projects:
```text
A problem was found with the configuration of task ':exposed-adt-mapping:dokkaGenerateModuleHtml' (type 'DokkaGenerateModuleTask').
- In plugin 'org.jetbrains.dokka.gradle.DokkaBasePlugin_Decorated' type 'org.jetbrains.dokka.gradle.tasks.DokkaGenerateModuleTask' property 'generator.dokkaSourceSets.main$0.sourceLinks.$0.remoteUrl' doesn't have a configured value.
Reason: This property isn't marked as optional and no value has been configured.
Possible solutions:
1. Assign a value to 'generator.dokkaSourceSets.main$0.sourceLinks.$0.remoteUrl'.
2. Mark property 'generator.dokkaSourceSets.main$0.sourceLinks.$0.remoteUrl' as optional.
```
Simply moving `map`s outside doesn't resolve this issue, probably because `Provider.map` is lazy not eager. So calling `Provider.set` inside them is not a good idea.
…iJ IDEA without success, by removing the module-wide opt-in and bumping the Gradle wrapper The Gradle error message when syncing in IntelliJ IDEA: ```text Execution failed for task ':kotlin-common-gradle-plugins:configurePrecompiledScriptDependenciesResolver'. > The value for property 'freeCompilerArgs' is final and cannot be changed any further. ``` This error doesn't occur when I run `publishToMavenLocal` or `check` from the command line. The commands work in the command line. See gradle/gradle#22091 which could be related.
…-error-free-compiler-args-final-and-bump-gradle-wrapper-to-v8.11.2' into kotlin-2.1.0-and-above Try resolving an error loading the Gradle project in IntelliJ IDEA 2024.3 and bump the Gradle Wrapper to v8.11.1 The bumped Gradle wrapper version is actually v8.11.1. "v8.11.2" in the branch name is incorrect.
…s on Kotlin 2.0.20
…unnecessary as it turns out, and the `implementation(platform(kotlin("bom")))` line without a Kotlin version has introduced a "Could not parse POM" build error in projects dependent on a project with one of these plugins applied via Maven since Kotlin 2.0.20
See commit 1648b7e and commit dc9d1c8 for more details.
Bump Kotlin to 2.1.0, Gradle to v8.11.1, and remove all the `app-conventions` plugins
… incompatibility issue
ShreckYe
changed the title
…sion` to the released stable version temporarily so the build can resolve in CI
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.