I think where you deploy to isn't in the settings.xml file because there there is no need for it. Where you get artifacts from does have a specific need.
It sounds like a nice to have feature, but I don't think there is a dire need for it from the community. > > But anyway, that is neither here nor there for me. The big problem > issue for me right now is why should I be forced to do everything > through a parent pom instead of in a settings.xml file? I don't > understand why certain settings should have to be in a pom that has to > be deployed.
