Quantcast
Channel: How to use Maven and various application.properties for artifact generation of different testing regions in a Spring configured app - Stack Overflow
Viewing all articles
Browse latest Browse all 4

How to use Maven and various application.properties for artifact generation of different testing regions in a Spring configured app

$
0
0

I want to use Maven to handle artifact generation for the different local and testing regions. I believe I can use different profiles but I am not certain.

In Maven can I select different directories to select files used on packaging (such as application.properties)? How would I set that up?

An idea of what I want is to have a the following folders for resources in my project

  • local
  • build server
  • dev
  • sys
  • prod

Each folder should contain a different version of application.resources which is a file in Spring that can be used to handle hard-coded strings for use in variables. For local builds- our developers also work on different operating systems. Should I require I want to make it seamless on different OS' also.

Key outcomes would be:

  • Control Maven lifecycle phases from inside the IDE (IntelliJ)
  • Not complicate phases and team processes
  • Keep things as consistent for each developer
  • Make the different configurations per developer/region appear invisible when running a phase e.g. install

Ideally I would have my project set up according to best practices (Duvall, Matyas, Glover).


Viewing all articles
Browse latest Browse all 4

Latest Images

Trending Articles



Latest Images