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
Is your feature request related to a problem? Please describe.
In order to build a generated Kotlin project on (Open)JDK 21, both the Gradle version and the Kotlin version have to be new enough. (Gradle 8.5 or higher, and Kotlin 1.9.20 or higher.) Unfortunately, even with version 7.2.0 of openapi-generator, quite outdated versions of the Gradle Wrapper (8.1.1) and Kotlin (1.8.x) are used. It does seem that at least a newer Kotlin version is used (1.9.20) when multiplatform is selected as the library option. But even then, the Gradle version is still outdated.
Describe the solution you'd like
It should be possible to override the default version of both the Gradle Wrapper as well as those of the Gradle plugins and dependencies in the generated Gradle build configuration.
Describe alternatives you've considered
First, I checked in the documentation whether there was already an option to do this, but I couldn't find any. Perhaps I missed it, and it's in other documentation somewhere? If so, please let me know. Thanks. 🙏
Wait for new versions of openapi-generator to be released, which hopefully generate projects with the newer versions, but we can't wait for that if we immediately require newer versions in the generated projects. It also increases the burden on the openapi-generator maintainers to release updates more regularly.
Use regex-based replacement logic to replace versions after the project is generated, which is tedious and increases the complexity of project build configurations.
Additional context
The current incompatibility of generated Kotlin Gradle projects with (Open)JDK 21 was the reason I ran into this, but there are many other thinkable scenarios in which it would be desirable to have the ability to override these versions. For example to upgrade dependencies that have vulnerabilities in the automatically generated versions.
Thank you kindly for considering this feature.
The text was updated successfully, but these errors were encountered:
volkert-fastned
changed the title
[REQ] Options to override Gradle Wrapper version and specific dependency versions
[REQ] Options to override Gradle Wrapper version and specific dependency and plugin versions
Feb 19, 2024
Is your feature request related to a problem? Please describe.
In order to build a generated Kotlin project on (Open)JDK 21, both the Gradle version and the Kotlin version have to be new enough. (Gradle 8.5 or higher, and Kotlin 1.9.20 or higher.) Unfortunately, even with version
7.2.0
ofopenapi-generator
, quite outdated versions of the Gradle Wrapper (8.1.1) and Kotlin (1.8.x) are used. It does seem that at least a newer Kotlin version is used (1.9.20) whenmultiplatform
is selected as thelibrary
option. But even then, the Gradle version is still outdated.Describe the solution you'd like
It should be possible to override the default version of both the Gradle Wrapper as well as those of the Gradle plugins and dependencies in the generated Gradle build configuration.
Describe alternatives you've considered
First, I checked in the documentation whether there was already an option to do this, but I couldn't find any. Perhaps I missed it, and it's in other documentation somewhere? If so, please let me know. Thanks. 🙏
Wait for new versions of
openapi-generator
to be released, which hopefully generate projects with the newer versions, but we can't wait for that if we immediately require newer versions in the generated projects. It also increases the burden on theopenapi-generator
maintainers to release updates more regularly.Use regex-based replacement logic to replace versions after the project is generated, which is tedious and increases the complexity of project build configurations.
Additional context
The current incompatibility of generated Kotlin Gradle projects with (Open)JDK 21 was the reason I ran into this, but there are many other thinkable scenarios in which it would be desirable to have the ability to override these versions. For example to upgrade dependencies that have vulnerabilities in the automatically generated versions.
Thank you kindly for considering this feature.
The text was updated successfully, but these errors were encountered: