jira-importer commented on issue #1112: URL: https://github.com/apache/maven-scm/issues/1112#issuecomment-2964646486
**[Sérgio Ozaki](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=serozaki)** commented Hello, let me try to explain why I have opened this topic and proposed this change. Comparing to git, the jazz workspace is equivalent to a git branch. There is not really a concept of repository in jazz like there is in git. In my use case I was trying to use the scm plug-in with the release plug-in. I had a "master" workspace and some other previous "release" workspaces that I had to support. The "master" workspace url was the one I kept in pom.xml and I didn't want to change it in the "release" workspaces, because it makes the merges a litlle bit easier. So when performing a release in the "release" workspace, the change sets (commits) with the release version and the next development version are created, but the release tag is created as a snapshot of the "master". So, the perform goal of the release plug-in checks out the "master" workspace and builds it instead of the "release". At first, the change I proposed made sense to me, but if you decide, I can revert it. -- 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]
