Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@strangesource
Copy link
Owner

whyoleg and others added 30 commits May 30, 2024 10:53
….13135.103) (Kotlin#3642)

The latest AA built with the newer version of IntelliJ Platform so we need to update it. This transitively requires updating a kotlin-compiler version used for kotlin K1 analysis because we share java analysis between K1 and K2 kotlin analyses.
Part of KT-64200

* update BioJava test task
- Re-introduce shared integration-test convention plugin, to de-duplicate common IT config.
- Add util for adding system properties & registering the values as appropriate Gradle task inputs.
  (This required replacing env-vars with system props.)
* fail test if Android SDK missing
* bump jgit
* fix devMavenRepositories caching
* fix ANDROID_HOME in AndroidIT
* move Dokka CLI JAR check into test (simplifies the Gradle config)
* fix ENABLE_DEBUG env var
* Refactor `fun MutableList<CommandLineArgumentProvider>.systemProperty()` to be more consistent with the other systemProperty utils, and so the intention is clearer.
* move test suite dependency `implementation(project())` to convention
* disable explicitApi in integration tests by default
* modify DevMavenPublishExtension#configureTask to configure Test task
List of changes:
* KT-65215 - Rename analysis-api-providers to `analysis-api-platform-interface`
* KT-69055
* KT-53669
* partially KT-67786
* partially KT-68882
* partially KT-68857
* KT-68341
* get rid of the `api-fe10`
* Update Analysis API to 2.0.20-dev-6911

List of changes:
- KT-68462
- partially KT-68884
and others

* Fix sequences

* Rename
Remove fastutil workaround as it doesn't any more depend on it
* Use JetBrains cache-redirector

Update both the Dokka project and integration test projects to use JetBrains cache-redirector.

* update Gradle update instructions
Update the GitHub Action to use the new specific Gradle task for testing BioJava introduced in Kotlin#3581.
…ng plugin (Kotlin#3693)

* Introduce a new parameter `olderVersionsDirName` in `VersioningConfiguration` to customise the directory name for older versions of HTMLs
* Add integration test with different folder names
…lin#3470)

* build: added ui kit files processing (Kotlin#3460)

* build: added linters to plugin-base-frontend (Kotlin#3460)

* chore: run frontend checks on pre-commit (Kotlin#3460)

* build: supported ts for ui kit in plugin-base-frontend (Kotlin#3460)

* build: store minified and unminified ui-kit (Kotlin#3460)

* chore: fixed eslint and ts errors in plugin-base-frontend (Kotlin#3460)

* chore: updated dependencies in plugin-base-frontend (Kotlin#3460)

* chore: fixed ts errors, removed ununsed in plugin-base-frontend (Kotlin#3460)

* refactor: extracted tabs styles to ui-kit (Kotlin#3460)

* build: store only minified js in ui-kit (Kotlin#3460)

* chore: updated stylelint, fixed errors in plugin-base-frontend (Kotlin#3460)
* build: added ui kit files processing (Kotlin#3460)

* build: added linters to plugin-base-frontend (Kotlin#3460)

* build: supported ts for ui kit in plugin-base-frontend (Kotlin#3460)

* chore: fixed eslint and ts errors in plugin-base-frontend (Kotlin#3460)

* chore: updated dependencies in plugin-base-frontend (Kotlin#3460)

* refactor: extracted tabs styles to ui-kit (Kotlin#3460)

* build: store only minified js in ui-kit (Kotlin#3460)

* chore: updated stylelint, fixed errors in plugin-base-frontend (Kotlin#3460)

* feat: introduced desgin tokens to ui-kit
* use `macos-latest` for `ui-showcase` build on CI

* fix DOKKA_TEST_OUTPUT_PATH

* Run integration test for `ui-showcase` only on macOS because of KMP with macOS targets
This will help reduce the GitHub Action cache pressure
Since Dokkatoo was first merged into Dokka, Dokkatoo has had several releases. It will be best to have a fresh start and merge Dokkatoo again from scratch. The first step is to remove the existing Dokkatoo subproject, which is currently unused and disconnected.

^OSIP-355
Update GitCheckoutTask, so it re-runs if the repo is dirty

Currently, GitCheckoutTask might not re-run if the checked-out repository is dirty. This can cause invalid test results.
So, update GitCheckoutTask to re-run if the repo does not exist, is invalid, or contains any modifications.

- return a result with a more detailed message
- add more logging
- when checking if a repo is valid, use the `.git` directory
- set `parameters.expectedCommitId = commitId`
adam-enko and others added 30 commits August 12, 2025 20:55
Also, suppress AbstractDokkaTask deprecation warning

---------

Co-authored-by: Oleg Yukhnevich <[email protected]>
* Fix DGPv2 versioning-multimodule-example

* rm Gradle wrapper files

* tidy readme

* mark previousDocVersions dir as generated

* update expected data

* exclude previousDocVersions dirs from git metrics

* mark v1 previousDocVersions dir as generated
Minor change - the short link already redirects to the same link.
…on (Kotlin#4182)

* Update Analysis API to 2.3.0-dev-1719

* Build `kotlin-analysis-symbols` module with the latest compiler version Kotlin#4178

* Use `lowercase`

* Fix unit tests to use the shadow stdlib from kotlin-analysis-*

* Update kotlinx-bcv to 0.18.1 for reading Kotlin metadata version: 2.2.0.

* [DGPv1] Use the shadow stdlib from kotlin-analysis-*

* [DGPv2] Use DokkaBootstrap to overcome gradle/gradle#34442

* Downgrade bcv to 0.17.0

* Fix DokkaGeneratorLoggingTest

* Increase metaspace in `MultiModule0IntegrationTest`

* Use org.jetbrains.dokka.enforceGradleKotlinCompatibility=false instead of BTA

* Get rid of `automagicTypedProxy`

* Increase metaspace a little

* Downgrade to 2.2.20-dev-6511

* Experiment: Use `-XX:SoftRefLRUPolicyMSPerMB=10` for stability
* Remove V2EnabledWithHelpers warning & info message

When users update to 2.1.0, V2EnabledWithHelpers is enabled automatically.

The info message was intended to nude people to migrate, but in 2.1.0 there's no need to nudge.
The other intention was to add links to the migration guide, but the deprecation message contains a link to the guide.

Without removing the message, we will require _all_ users to suppress the warning.
This is an annoyance, and we should just remove the message.

* update tests

* Simplify MigrationMessagesTest
Adds Gradle 9.0.0 to the tested Gradle versions set.
Additionally:
* bumps Gradle 8 version to the latest minor release 8.14.3
* bumps KGP 2.1.0 to the latest minor release 2.1.21
* adds KGP 2.2.0
* adds a workaround for KT-77218 in tests


Fixes Kotlin#4150
…#4214)

* Add test for KDoc links in module/package documentation Kotlin#4191

* [K2] Fix resolving KDoc links in module/package documentation
Fixes Kotlin#4194
Fixes Kotlin#4195

* Fix compatibility with JDK 25 by properly packaging the correct `JavaVersion` from the kotlin compiler
* Allow usage of `Unsafe` inside DGPv2 worker to not emit warning on JDK 24+
* Create an empty `javadocJar` by ourselves; otherwise using `withJavadocJar` will cause Gradle to execute the `javadoc` task, which will not work
Fixes Kotlin#3775

* Add more tests for `>`
* Make regex replacement for blockquote to be performed only when we are inside of a blockquote
* Additionally, it could improve the performance (and memory pressure) of Markdown parsing a bit, as we don't create three `Regex`s anymore on each text processing
* Enable K2 analysis by default
* Log a warning when K1 analysis is enabled.
* Set org.jetbrains.dokka.experimental.tryK2 in tests unconditionally to use the right analysis mode in tests, like continuing using K1 mode in K1 tests
* Update test data

Partially addresses Kotlin#4190

---------

Co-authored-by: Alexander.Likhachev <[email protected]>
* Update publication URLs to the new instance
* Drop direct publication to MavenCentral
…ntAs (Kotlin#4226)

* Fix expect/actual wrong way around in shouldBeADirectoryWithSameContentAs

* update tests
* Use the shadowed stdlib in the Dokka Maven Plugin

* Excluding services files of aalto from `analysis-kotlin-symbols`

* Use the shadowed `analysis-kotlin-symbols`
* Update Analysis API to 2.3.0-dev-5493

* Fix the test `K2 full link should lead to an extension with type params`
Kotlin#3680

* Use KDoc tag subject name when rendering `@see` tags

* Use KDoc tag subject name when rendering `@see` tags in K1 mode

* Use KDoc tag subject name when rendering `@throw` and `@exception` tags

* Use markdown tag content name when rendering `@see`, `@throw` and `@exception` tags

* Update how `@throws` and `@exception` tag render: now they always use tag name instead of FQ

---------

Co-authored-by: Oleg Yukhnevich <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.