jira-importer commented on issue #661: URL: https://github.com/apache/maven-scm/issues/661#issuecomment-2964611864
**[Petter Måhlén](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=petterm)** commented The way we use it at work, we do have a central repository so for us I would say pushing (of + to the current branch only) is desirable or at least ok. Off the top of my head, I can't think of any real issues with not pushing - we could just do that manually. Even for more truly distributed source management, though, I would say that the nature of making a release involves publishing the artifacts, so it would make some sort of sense to also publish the source code (in a better way than a jarball Maven artifact). But I guess that part of it could be seen as a separate thing - if somebody wants the tag that corresponds to the released code, you just have to pull it from whoever happened to make that release. So from my perspective, Brett's suggestion about not pushing sounds fine. On another note, I would hate to work on a combination of Maven + completely distributed source. :) Handling SNAPSHOT releases would be hell, or at least, you couldn't do it using a shared repo. Even without a central repo for snapshots, conflicts where my project A version depends on a project B 1.2-SNAPSHOT that is completely different from somebody else's project B 1.2-SNAPSHOT are likely and hard to troubleshoot. I guess some addition to Maven's snapshot concept would be required for that to work. -- 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]
