Micronaut 5 Release Themes #12008
Replies: 8 comments 10 replies
-
My suggestions:
Regarding Kotlin and KAPT, we will simply remove all the tests that are not Kotlin 2 KSP 2 |
Beta Was this translation helpful? Give feedback.
-
Removing KAPT means no PicoCLI?! |
Beta Was this translation helpful? Give feedback.
-
Are there plans to promote the "experimental mode to run virtual threads on the Netty event loop" feature to stable? |
Beta Was this translation helpful? Give feedback.
-
I've noticed experimental work in Micronaut's codebase for supporting Kotlin suspend functions in AOP tools, but I couldn't get it to work. In our project, we abandoned coroutines due to the lack of proper support for suspend functions in Micronaut's AOP tools, despite appreciating Kotlin's coroutines and async capabilities. We switched to virtual threads, which mainly avoid the need for suspend but lack other benefits of coroutines. Is there community interest in improving support for Kotlin suspend functions in Micronaut's AOP tools? Thanks |
Beta Was this translation helpful? Give feedback.
-
we have project board with other issues where we should organise work: |
Beta Was this translation helpful? Give feedback.
-
Please, divide core repo to micronaut-core and micronaut-http. Core repo now is so fat! |
Beta Was this translation helpful? Give feedback.
-
Also, don't forget these PRs: |
Beta Was this translation helpful? Give feedback.
-
Also, it's time to fix childhood illness: #10512 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The discussion here is for the release of Micronaut 5.
Currently it is a priority to avoid breaking changes to the framework and ensure an easy upgrade. That said certain third party dependencies have moved on to new major versions that may include upgrade requirements.
APIs deprecated in the 4.x line will be removed.
Micronaut 5 will upgrade third parties and define a new baseline Java version.
Third Party Dependency Upgrades
Enhancements
Nullable
annotation (but retain latter to avoid breaking changes)Deprecated and Removed Core Features
The following features will be removed from core:
Breaking Changes Under Consideration
Breaking changes in either the API or behaviour will be kept to a minimum. The following rules will be followed:
@Deprecated(forRemoval)
The following modules are being considered for deprecation:
Beta Was this translation helpful? Give feedback.
All reactions