I wonder what is the Maven way in my situation.

My application has a bunch of configuration files, let's call them profiles. Each profile configuration file is a *.properties file, that contains keys/values and some comments on these keys/values semantics. The idea is to generate these *.properties to have unified comments in all of them. My plan is to create a template.properties file that contains something like

#Comments for key1/value1
key1=${key1.value}

#Comments for key2/value2
key2=${key2.value}

and a bunch of files like

#profile_data_1.properties
key1.value=profile_1_key_1_value
key2.value=profile_1_key_2_value

#profile_data_2.properties
key1.value=profile_2_key_1_value
key2.value=profile_2_key_2_value

Then bind to generate-resources phase to create a copy of template.properties per profile_data_*, and filter that copy with profile_data_*.properties as a filter.

The easiest way is probably to create an ant build file and use antrun plugin. But that is not a Maven way, is it?

Other option is to create a Maven plugin for that tiny task. Somehow, I don't like that idea (plugin deployment is not what I want very much).