-
Notifications
You must be signed in to change notification settings - Fork 405
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
Dokka Gradle Plugin 2 #2839
Draft
aSemy
wants to merge
174
commits into
Kotlin:master
Choose a base branch
from
aSemy:feat/gradle-plugin-2
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Dokka Gradle Plugin 2 #2839
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
…ser matching usage in gradle.kts files)
…tion configuration into DokkaPlugin. Use Gradle managed types to auto-configure some task properties
…' into feat/gradle_dokka_executor_service
…ntion_plugins # Conflicts: # build.gradle.kts
…a different implementation on Kotlin 1.6)
… JSON encode some config
- create DokkaPublication to handle each Dokka output - for each DokkaPublication, create format specific tasks/configurations/etc - create specific plugins for each Dokka output format - do a tonne of refactoring to get conventions working... - add @nested to some task props - group Gradle utils in a file
I've made lots of progress, and I have decided to split off this PR into a separate project. https://github.com/adamko-dev/dokkatoo#readme It's very experimental and unstable, but it's available for anyone who wants to try it out! Under the hood it still uses Dokka, but not the Dokka Gradle Plugin. |
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.
A draft re-write of the Dokka Gradle Plugin.
I've made lots of progress, and I have decided to split off this PR into a separate project.
https://github.com/adamko-dev/dokkatoo#readme
It's very experimental and unstable, but it's available for anyone who wants to try it out!
Under the hood it still uses Dokka, but not the Dokka Gradle Plugin.
This implements most of #2700
It's an early draft, so I'm not looking for specific feedback, I just wanted to share, because hopefully it provides a more clear goal when discussing #2700.
The new plugin doesn't directly compare to the existing plugin, as I haven't yet implemented the existing configuration DSL - but that is the plan! Once that's done, it will be easier to compare and contrast.
I've implemented the re-written plugin in a separate project, and I've added other Gradle Plugin improvement PRs, because it helps me during development to compare and contrast the code. But because the new plugin is in an 'included build', these other PRs aren't necessary - the plugin is completely independent.
TODO