-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Migrate to DGPv2 #4436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Migrate to DGPv2 #4436
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
4d6ac73
Workaround to make project importable.
qwwdfsad b4c4f46
Migration to DGPv2
qwwdfsad 8d1525e
TODO
qwwdfsad 8d3cc55
Update buildSrc/src/main/kotlin/dokka-conventions.gradle.kts
qwwdfsad 7c6e5ff
Dokka 2.0.0
whyoleg 1c9b082
Rename function back to it's original name to reduce diff
whyoleg f2167c4
Remove workaround for KT-71784
whyoleg 5c3a04d
Simplify templatesDir configuring
whyoleg 63e88d4
Cleanup `dokka-convention`
whyoleg c5f2051
Drop local package list as it's better to use remote one
whyoleg 06b0df2
Fix external links in rx modules
whyoleg a179bb7
Fix knit
whyoleg File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@adam-enko, this is still required. Could you check what happens here?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked out your branch, commented out this code, and ran
gradle :kotlinx-coroutines-core:dokkaGenerate
but didn't see a problem. How can I trigger the error?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, okay, I needed to run
gradle :dokkaGenerate
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what the problem is, and it's hard to figure out.
I'm just speculating, but maybe somehow DGP automatically registers the Dokka SourceSets before KGP has finished creating the
jvmJar
task, and so the task dependencies aren't correct. I don't know how this could happen, but it seems to describe the result.If I were to guess, it's because the buildscripts are using cross-project configuration (
allproject
/subproject
) and internal Gradle utilities (org.gradle.kotlin.dsl.support.delegates.ProjectDelegate#configure
), so the plugins aren't applied in the correct order.I think the only way to fix this is to update the buildscripts so they don't use discouraged practices.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I understand,
:kotlinx-coroutines-core:dokkaGenerateModuleHtml
should not depend at all on:kotlinx-coroutines-core:jvmJar
in main source sets, because it should rely on sources of the current module + classpath of dependencies.Another idea could be that
jvmJar
is needed for one of the test source sets, which is created by KGP, and so added as a Dokka source set, but those are suppressed, and I thought that it should not affect the inputs of thedokkaGenerateModuleHtml
task. But maybe I'm wrong, and even if the source set is suppressed, it will affect inputs?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In any case, I would say it's not blocking the migration to DGPv2