[ 
https://issues.apache.org/jira/browse/SCM-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962725#comment-17962725
 ] 

ASF GitHub Bot commented on SCM-724:
------------------------------------

jira-importer commented on issue #927:
URL: https://github.com/apache/maven-scm/issues/927#issuecomment-2964633392

   **[Chris 
Graham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=chrisgwarp)**
 commented
   
   Hi All.
   
   The base jazz code has not changed much, so it will continue to produce the 
same results.
   
   If it's still happening, could you please run mvn -X release:prepare 
release:perform?
   
   That will dump the execution of the scm commands to the console log.
   
   Then it's a matter of working out what commands are failing (and why). You 
also need to confirm that the scm deliver is being executed.
   
   Does the release (excluding the scm issues here) complete successfully? Or 
does it fail with an error.
   




> pushChanges not working with maven-scm-provider-jazz
> ----------------------------------------------------
>
>                 Key: SCM-724
>                 URL: https://issues.apache.org/jira/browse/SCM-724
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-jazz
>    Affects Versions: 1.7, 1.8, 1.8.1
>         Environment: Client on windows 7
> Jazz RTC version 4.0.1 (for server and scm)
>            Reporter: Oscar Picasso
>            Assignee: Chris Graham
>            Priority: Major
>
> 1- maven-release-plugin configured with <pushChanges>true</pushChanges>
> 2- the RTC repository workspace for the releases has a default/current stream 
> as target flow
> 2- execute
> mvn release:prepare release:perform
> After release completion:
> - changes performed on the RTC repository workspace are not delivered to the 
> target stream
> - the ownership of the RTC snapshot created during the release has not been 
> changed to the target stream
> According to the documentation it seems the changes should be propagated to 
> the target stream.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to