You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Atrium is currently using dokka 0.9.8 via the tutteli-dokka plugin.
We would like to update to dokka 1.4.10
Following the things we need to do (see #683 most likely you can build on this):
remove classpath "ch.tutteli:tutteli-gradle-dokka:$tutteli_plugins_version" from build.gradle
configure the new dokka plugin instead. You don't have to bother what was configured before, you can start from scratch but we have the following requirements:
we need only the html report (disable the rest)
make sure it is not included in the normal build (./gradlew build should not trigger it) - might be this is already the case. Use ./gradlew atrium-core-api-jvm:build --dry-run and check if dokka is included. If it is, then find ways to deactivate it. We want to be able to run dokka separately
check if the samples for toBe are correctly rendered
Write a comment I'll work on this if you would like to take this issue over.
This way we get the chance to revise the description in case things have changed in the meantime, we might give you additional hints and we can assign the task to you, so that others do not start as well.
Do not hesitate to ask questions here or to contact us via Atrium's slack channel if you need help
(Invite yourself in case you do not have an account yet).
The text was updated successfully, but these errors were encountered:
Non-Code related feature
Atrium is currently using dokka 0.9.8 via the tutteli-dokka plugin.
We would like to update to dokka 1.4.10
Following the things we need to do (see #683 most likely you can build on this):
classpath "ch.tutteli:tutteli-gradle-dokka:$tutteli_plugins_version"
from build.gradle./gradlew atrium-core-api-jvm:build --dry-run
and check if dokka is included. If it is, then find ways to deactivate it. We want to be able to run dokka separately=> make sure we still suppress the packages defined at the end of the gh-pages.gradle script.
Hint, the following might help to setup the plugin, note thought that Atrium is using groovy and not kotlin for gradle
https://github.com/Kotlin/dokka#using-dokka
Your first contribution?
I'll work on this
if you would like to take this issue over.This way we get the chance to revise the description in case things have changed in the meantime, we might give you additional hints and we can assign the task to you, so that others do not start as well.
(Invite yourself in case you do not have an account yet).
The text was updated successfully, but these errors were encountered: