Quarkus 0.27.0 released - More Amazon Lambda goodness

We were hard at work to get the Amazon Lambda features on par with the Azure Functions ones. You can now use traditional Lambdas or RESTEasy/JAX-RS/Servlet based ones and create your new Lambda projects with simple Maven archetypes.

And…​ we also added native support!

Learn more about all this in our new guides for Amazon Lambda and Amazon Lambda with Vert.x Web, Servlet, or RESTEasy.

Love live coding with our dev mode? It now detects the changes to your pom.xml and reloads the application for you.

We made a major change in how the project outputs (jars, native images) are produced: they are produced one at a time to allow for maximum flexibility and pave the way for output-specific optimizations.

In practice, it won’t change things for you except for one use case: if you build a native image, we won’t build the runner jar at the same time anymore. Two distinct builds are required.

As a consequence of this change, if you use Docker to build your native images, use the following command from now on:

We used to have a mix of javax. and jakarta. artifacts in Quarkus: we have now moved everything to Jakarta.

If your application uses dependencies outside of the Quarkus extension ecosystem, you might now see a warning message saying you are using non recommended artifacts. We warn you so that you don’t end up with duplicate implementations of the same classes in your project, which could lead to weird problems. If you are in this case, follow the advice we give you in this warning message and add exclusions/explicit dependencies.

This is a new feature so if you are seeing something weird, report it on the quarkus-dev mailing list.

Thanks to several improvements made to the Kubernetes extension, you now have a lot more flexibility in how you customize the Kubernetes manifests via our central application.properties: learn more about it in the updated documentation.

Moreover, OpenShift manifests can also be generated by the extension.

@SubstrateTest has been deprecated: use @NativeImageTest instead.

If you are an extension author, all the native image-related build items have been renamed: they are now in a nativeimage package instead of substrate and, if their name contained Substrate, you should just replace Substrate with NativeImage in the name. We deprecated the old build items, they will be removed at a later stage.

The war launcher has been removed. We don’t think anyone was using it but let’s be thorough.

We also fixed bugs and usability issues: get the full changelog of 0.27.0 on GitHub.