[
https://issues.apache.org/jira/browse/SCM-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811569#comment-16811569
]
Sérgio Ozaki edited comment on SCM-889 at 4/6/19 12:36 PM:
-----------------------------------------------------------
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.
was (Author: serozaki):
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 in 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.
> Jazz tag command creates snapshot in wrong workspace
> ----------------------------------------------------
>
> Key: SCM-889
> URL: https://issues.apache.org/jira/browse/SCM-889
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-jazz
> Affects Versions: 1.9.5, 1.10.0
> Reporter: Sérgio Ozaki
> Assignee: Chris Graham
> Priority: Major
> Fix For: 1.11.1
>
>
> Jazz provider tag command uses the jazz workspace set int the pom.xml scm
> tag. When in other jazz workspace, the snapshot is not created based on the
> current work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
