What technology to manage evolutive configurations on 1-tier software

I have a Java application software that evolves. It uses a configuration file at launch to load configuration values. As the software evolves, the configuration evolves too. Some keys are no longer used, new keys are added, eventually some keys are renamed, some values have different type.

The question is, what it the best technology to use for configuration management in my case?

The requirements are:

• store and load configuration information to and from one file,
• manage complex values (such as maps),
• manage missing values,
• manage evolution in value types,
• manage key renaming,
• manage no longer used key/value pairs.

So far, YAML did not meet all listed requirements.

Could XML with JAXB marshaling and unmarshaling meet the requirements or will I encounter problems there too?