Environment-Specific Configuration Values During a Jenkins + Maven Build

I’m ( Trying :) ) to build an automatic deployment pipeline using Jenkins and Maven, and I’m looking for best practices around handling environment-specific configuration.

Scenario:

I have a Java application that needs to be built and packaged using Maven.

Before the build/package step, certain configuration values must be replaced based on the target environment (e.g., dev, test, prod).

For example, in one of the Java configuration files, a placeholder like LOAD_BALANCE_URL needs to be replaced with an environment-specific value before the application is built and packaged.

Goal: I want a clean and maintainable way to:

Inject or replace configuration values during the Jenkins build process

Ensure the correct values are applied based on the target environment

Avoid hard-coding environment-specific values in the source code

Question: What are the recommended approaches to achieve this using Jenkins and Maven?
Should I be using Maven profiles, resource filtering, Jenkins environment variables, or another best practice?

Any examples or guidance would be appreciated.

java code1 configuration.properties LOAD_BALANCE_URL=<LOAD_BALANCE_URL> java code2 configuration.properties USER_NAME=<USER_NAME> config location in GIT PROD_CONF.properties LOAD_BALANCE_URL=http://PROD.server.com USER_NAME=PROD_USER UAT_CONF.properties LOAD_BALANCE_URL=http://UAT.server.com USER_NAME=UAT_USER QA_CONF.properties LOAD_BALANCE_URL=http://QA.server.com USER_NAME=QA_USER