Imagine that a Maven POM configures a set of integration tests for web apps (could be a functional test as well).
- in developer context, you would clearly use Chrome and configure that accordingly
- in the CI, you want a headless test with another browser driver
Same would be if you decide to configure all fixed dependencies' versions in on place, and for a specific stage/release.
For such cases, what is the best strategy to have environment-specific POM properties files for Maven, and is it a good approach?