2.0.0 Release
Eureka 2.0.0 Release Notes
Eureka 2.0.0 has been released. This release is a new effort and is not related to a previous preview of code released in the 2.x-archive branch which was an experimental re-architecture of Eureka.
The Eureka Server HTTP API and wire data formats have not changed for the 2.0.0 release. Eureka servers and clients should be backwards and forwards compatible over the wire. This release was primarily driven for compatibility with Spring Framework 6.0 and Spring Boot 3.0 and the change to Jakarta EE 9.
What has changed?
The Eureka 2.0.0 Java client API is not backwards compatible with 1.x.
Eureka 1.x included support for Jersey 1 and optional Support for Jersey 2. In many cases, Jersey 1 was the default and was baked into the eureka-core
and eureka-client
modules. Having a default client has been removed. The new eureka-client-jersey3
and eureka-core-jersey3
should now be used if no other implementation is provided (such as Spring Cloud support for a RestTemplate
implementation).
The DiscoveryClient constructors
have been updated to have a new required TransportClientFactories
parameter. The majority of the Eureka 2.0.0 Java client API has remained unchanged.
All references to javax.*
classes have been changed to jakarta.*
classes and the appropriate modules have been added.
The eureka-server-governator
module was removed. There is no current support for the JakartaEE version of @Inject
.
The eureka-server
module currently does not build a functional WAR file. The recommended way of creating a Eureka 2.0.0 server is via Spring Cloud Netflix as a Spring Boot application.
The build now requires JDK 11 because of some tests that require Jetty and the version of Jetty that supports Jakarta EE 9 requires Java 11. The build still targets Java 8.
Feedback
Please try things out and provide any feedback or issues at https://github.com/Netflix/eureka/issues.