Currently explicit staging profile selection bypasses any repository target set in a staging profile. This is OK for some use cases, but for others it gives end users the ability to deploy artifacts with group ID's that they should not have access to.
Disabling explicit profile selection as a workaround isn't always an option, because some nexus-staging-maven-plugin goals require it. An example of this is "deploy-staged-repository".
We should consider adding a mode to staging that allows explicit staging profile selection, and yet still enforces the staging profile's repository target.