release:prepare does not pass argument "--settings" with current settings.xml to inner maven

The impact is that release:prepare tries to use $HOME/.m2/settings.xml instead of the one supplied by --settings cmdline option, which leads to unexpected behavior
Of course if it does not exist, the inhouse repository is avoided and release often fails due to a ResourceDoesNotExistException when an inhouse artifact is requested by the pom.

To reproduce this problem, just rename your ~/.m2/settings.xml to ~/.m2/s.xml and run this:
mvn --settings=$HOME/.m2/s.xml release:prepare .....