Hi Mark… yes, we are an enterprise team, and have a standard in place to access the Nexus credentials from the settings.xml file in a consistent way, regardless of the build mechanism. We support the usual, Ant, Maven, MSBuild, Gradle, and PowerBuilder build types. We also support multiple versions of Maven, so the path to the settings.xml, if used, can vary for build types. We have been able to accomplish what was needed keeping the settings.xml available on the build servers themselves, without propagating the file/credentials out to individual app teams. So, are we saying that your Maven Settings Plugin will support the cmd line approach, passing in a location other than the GLOBAL or USER default locations?