loop in dev@ could be a solution using webdav cloudbees private location ?
Yes. That's what we currently do for credentials for Maven, for example - they're in a private settings.xml file. That's also I think what we would do for publishing snapshots to the Apache repo.
Replacing the parent POM, by the way, will mean that we will need to add a couple of settings that are currently inherited from the Sonatype POM to our project POM to ensure we can still release to Maven Central.
Create a JIRA issue for this? ap
