aboutsummaryrefslogtreecommitdiff
path: root/plugins/android-documentation/build.gradle.kts
AgeCommit message (Collapse)Author
2023-08-30Migrate to JUnit 5 and unify used test API (#3138)Ignat Beresnev
2023-08-28 Support Dokka K2 analysis (#3094)Vadim Mishenev
Dokka has its own documentable model to represent analyzed code. The analysis is performed by a compiler frontend. In K1 the compiler frontend has descriptors that use the underlying Binding Context (global shared stateful structure). Dokka just maps descriptors to Documentable by DefaultDescriptorToDocumentableTranslator. K2 compiler has FIR tree, which means “Frontend Intermediate Representation”, instead of Binding Context. But we do not use FIR in Dokka directly, since it is too low-level for analysis. The Kotlin compiler provides high-level Analysis API for this case. The API is used by KSP too. Analysis API represent elements of FIR (declarations, parameters and so on) as Symbols. For more details see KtSymbolByFirBuilder, KtSymbol. For Dokka symbol is the replacement of descriptor in K2. Also, to set up the environment of project analysis in K1 we use idea dependencies (or copy-past from there). In K2 for these aims, there is a Standalone mode for Analysis API.
2023-07-05Decompose Kotlin/Java analysis (#3034)Ignat Beresnev
* Extract analysis into separate modules
2023-03-27Mark utilities.* API as Dokka-internal (#2937)Vsevolod Tolstopyatov
* Deprecate unused declaration, remove inline declaration (as it's binary compatible), opt-in into internal API at project level * Opt-in into DokkaInternalApi where applicable * Get rid of intermediate test-utils module
2023-03-17Introduce Gradle Version Catalog with type-safe project dependencies (#2884)aSemy
2023-03-13Migrate buildSrc to composite build (#2912)Goooler
2023-03-07Use buildSrc convention plugins to configure the Dokka subprojects (#2704)aSemy
2021-03-01Suppress tag support (#1742)Marcin Aman
* Suppress tag support * Support Hide tag in javadoc * Extract hide tag to be in separate plugin