looks like my point is not fully clear:
We have a ant based build in a Jenkins continuous integration system. To feed the needed information into Sonar we generate a pom.xml during the build typically into the directory /build/sonar/pom.xml. The build directory is our equivalent to the maven target directory. So we will definitely not put /build or anything below under version control. Also since the pom.xml is generated our policy does not permit to place the file outside the build directory.
In other words: Our base directory is under version control, but the pom.xml is not placed in our base directory.
With the current behavior the plugin will fail for every build that uses the -f prj/build/sonar/pom.xml option that points to a file outside of version control. And it might produce unpredictable results if the pom.xml is not placed in the base directory of the project.
I assume this is very common for none maven builds.
Might be a parameter that points to the base directory of the project might help to solve this? Default can stay as is - the directory where the pom.xml is placed.