azalea/kotlin-fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Explain issues with local.properties in verification metadata update

Browse Source
This commit is contained in:
Marco Pennekamp
2024-02-12 18:27:19 +01:00
committed by Space Team
parent 9ff6dcbe0a
commit 08332fdc6e
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ReadMe.md
+7 -2
View File
@@ -143,11 +143,16 @@ sed -i -e '/<components>/,/<\/components>/d' gradle/verification-metadata.xml
./gradlew -i --write-verification-metadata sha256,md5 -Pkotlin.native.enabled=true resolveDependencies
```
*`resolveDependencies` task resolves dependencies for all platforms including dependencies downloaded by plugins*
*`resolveDependencies` task resolves dependencies for all platforms including dependencies downloaded by plugins.*
- If you’re adding a dependency with OS mentioning in an artifact name (`darwin`, `mac`, `osx`, `linux`, `windows`), remember to add them to
Keep in mind:
- If you’re adding a dependency with OS mentioned in an artifact name (`darwin`, `mac`, `osx`, `linux`, `windows`), remember to add them to
`implicitDependencies` configuration or update `resolveDependencies` task if needed. `resolveDependencies` should resolve all dependencies
including dependencies for different platforms.
- If you have a `local.properties` file in your Kotlin project folder, make sure that it doesn't contain `kotlin.native.enabled=false`.
Otherwise, native-only dependencies may not be added to the verification metadata. This is because `local.properties` has higher
precedence than the `-Pkotlin.native.enabled=true` specified in the Gradle command.
## Using -dev and -SNAPSHOT versions