Affects Version/s: 2.11.0
Fix Version/s: 2.12.0
When performing a release management, it always promote the pom file even if configured to use different xml file.
Steps to reproduce:
1. Create a pom-test.xml file.
2. Run the build within Jenkins and point to that file.
3. Run Release management. The pom.xml file will be promoted instead of the pom-test.xml file
If the pom.xml does not exists, the release management will fail with no file exists error.