korlibs / korlibs/korge-plugins
KorgeGradlePlugin changes the project version
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Hello and thank you for your awesome game engine.
When you apply the plugin in Gradle, the project version is set to "4.10.1". This was very frustrating when using the maven-publish plugin (the version was always 4.10.1). I'm not a Gradle expert, but it seems a bug to me.
To reproduce the issue, download the korge-hello-world project and add the following lines around apply<KorgeGradlePlugin>() in build.gradle.kts:
version = "0.1"
println(version)
apply<KorgeGradlePlugin>()
println(version)
Output is:
> Configure project :
0.1
Kotlin Multiplatform Projects are an experimental feature.
4.10.1
Tested with versions 1.14.0.0 & 1.15.0.0 of the plugin.
The workaround I found is to set the version of the project after applying the plugin.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce this in the korge-hello-world project's build.gradle.kts using the version assignments around apply() shown in the issue. Start at the KorgeGradlePlugin entry point and trace where it changes the project version. Done means the version remains 0.1 after applying the plugin and maven-publish uses that value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100