jira-importer commented on issue #1112: URL: https://github.com/apache/maven-scm/issues/1112#issuecomment-2964646487
**[Chris Graham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=chrisgwarp)** commented Thank you for responding [Sérgio Ozaki](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=serozaki)! The code was originally written to honour the pom.xml, and I think that it should continue to be, as this change will change the existing workflow/patterns already in place. I wrote some documentation and suggestions on how to best use the release plugin with Jazz, read it [Using the Release Plugin with the Jazz SCM provider](http://maven.apache.org/scm/maven-scm-providers/maven-scm-provider-jazz/releases.html). That was 4 years ago (before I was using this in a CI env). In a CI env, Jenkins or even Jazz's own, I would rename the *BuildWorkspaces to *ReleaseWorkspaces to make it clearer. If you do have CI in place (and not Jazz's private builds), then I would have both the *BuildWorkspaces (for the usual CI SNAPSHOT builds) and the *ReleaseWorkspaces to perform your releases in. If you have the flow targets set up correctly, then the changesets commits and tags should be pushed up to a stream. The Jazz equivalent of a tag is a Snapshot which is across all components in a repository workspace, which is why only one component in each *BuildWorkspace (should be renamed *ReleaseWorkspace). The concern here about your change is that it relies upon local setup not captured in the pom, which may lead to non repeatable builds. In your case, it's clear: the workspace in the pom does not need to be changed. It simply needs to be the release workspace, not your 'master' which should probably be a Stream anyway. I would also caution against direct comparisons with Git, Perforce, ClearCase or other similar SCM's. Each are different, some radically so. I would encourage you to think in Jazz terms, not compare against other SCM's. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
