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.
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
simplify sample usage #623
base: master
Are you sure you want to change the base?
simplify sample usage #623
Changes from 7 commits
90fb598
714321a
a71d857
3720208
dd18d15
ba26f75
6530d5e
288c840
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume, when we develop Skiko - there is no point to use Skiko from maven repo. And if users just copy the example, it will work too.
This change will simplify the whole process:
./gradlew run
). It will work as in our use case, and in user's use case (when they copy the example)If we do this change, we can (and should) simplify the Readme and the CI file - there will be no need to call
publishAllSkikoJvmRuntimeToMavenLocal
and defineskiko.version
.Also, because of this, we can remove
skiko.version
property completely, and just use0.7.41
constant instead of it.(we can discuss this online, to sync on the final decision)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a good suggestion. But we have problems with this case.
includeBuild("skiko")
provides onlyorg.jetbrains.skiko:skiko:1.2.3
artifact.When we run task
publishAllSkikoJvmRuntimeToMavenLocal
, under the hood this task downloads and packs skia inside jar and saves to mavenLocal several additional dependenciesorg.jetbrains.skiko:skiko-awt-runtime-macos-arm64:1.2.3
,org.jetbrains.skiko:skiko-awt-runtime-macos-x64:0.0.0
,org.jetbrains.skiko:skiko-android-runtime-arm64:1.2.3
and others.Also, we have task
publishSkikoWasmRuntimePublicationToMavenLocal
to saveorg.jetbrains.skiko:skiko-js-wasm-runtime:1.2.3
I think we also can solve this problem, but I don't know how...
For this case, we need to rewrite publishing tasks and also provide modules instead of jars:
skiko/skiko/build.gradle.kts
Line 1232 in 90fb598