Open rsvoboda opened 1 month ago
That's not the purpose of quarkus update
. We only apply changes that are strictly necessary for the app to work with the new version.
If you are happy with the versions you use, that's all fine. We update a plugin when we absolutely need a new version of the plugin for it to work for instance. In the same way, we won't move you to Java 21 or adjust your code to modernize it.
As for the native-image
thing, we could probably implement a specific recipe for that but I'm not entirely sure it's worth the trouble nor it in line with the quarkus update
objectives.
/cc @ebullient (cli), @maxandersen (cli)
Describe the bug
Quarkus update doesn't update the 3.8 sample app to a similar level as the 3.15 sample app
Expected behavior
Updated 3.8 sample app is equivalent to the 3.15 sample app
Actual behavior
Quarkus update doesn't update the 3.8 sample app to a similar level as the 3.15 sample app
Differences in upgraded
pom.xml
:<compiler-plugin.version>3.12.1</compiler-plugin.version>
vs3.13.0
in 3.15 sample app<surefire-plugin.version>3.2.5</surefire-plugin.version>
vs.3.3.1
in 3.15 sample app<goal>native-image-agent</goal>
in quarkus-maven-plugin definitionHow to Reproduce?
quarkus update
Output of
uname -a
orver
macOS
Output of
java -version
Java 21
Quarkus version or git rev
Quarkus 3.15.1
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response