jira-importer commented on issue #486: URL: https://github.com/apache/maven-scm/issues/486#issuecomment-2964598469
**[Jerome Lacoste](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=lacostej)** commented [accidently fired the form in the middle of my former comment. Here it is, completed] Sorry but I am not satisfied. Having to remember if project a project defines a non developer connection or not is counter intuitive. I don't see a real explanation of why this automatic fallback shouldn't be implemented. What would that break? Isn't a read-write connection also a read connection? Being able to do scm:update whatever the pom contains sounds closer to the maven philosophy to me. So to me, there should be an automatic fallback mecanism. If fallback by default is not an option, consider something like mvn scm:update -DconnectionType=fallback As long as I can put this default option somewhere in my maven config and not have to type it again, I will be satisfied. Would something like that be OK? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
