We are providing settings file to Maven with -s command line parameter. This works fine everywhere except for archetype plugin in create-from-project goal.
Plugin works fine until it comes to archetype post-phase where it obviously runs Maven again but without passing -s command line parameter and therefore ignores settings file location.
This breaks our build as we are using repository manager specified in settings file and central Maven repository is not visible for the build server directly. Therefore plugin can't download its dependencies and/or update timestamp.
We can not use default settings file location on the build server as other teams use it with different settings and this is not allowed and there is no way to work in that way as a workaround.