Adding eureka server and eureka client dependencies is a faulty situation!

When using Eureka Client in Spring Cloud applications, the order of dependencies in your pom.xml can cause startup issues.

Problem

You may encounter errors starting your Eureka client service even when you have only the client dependency (not the server). This typically happens when "Internal dependencies" are listed first in your pom.xml.

Solution

Rearrange your dependencies in the following order:

1. Spring Boot Starters

2. Spring Cloud dependencies

3. Internal dependencies

4. Other dependencies

This order ensures proper dependency resolution and prevents startup conflicts between your Eureka client configuration and other components.