Problems encountered with the RTC and MAVEN release plugin

On the MAVEN site there is an article on how to automate release using jazz SCM plugin (jazz release), and I'm not going to talk about it, mainly about the problems and how to deal with this after use. File structure issues, at the beginning of our system design, 3 components,3 Maven project was created in the RTC to build 3 ears independently, and then a fourth component was built to build 3 ears at a one-time (build) specializes in storing Pom.xml and settings.xml. The structure is as follows:
Component1
Project1
Component2
Project 2
Component3
Project 3
Component4
Build Project
Pom.xml, Settings.xml
So after the improvements, our MAVEN commands are in the Bui LD directory. At this point in our build project, Pom.xml added the following configuration:

   <scm>             <connection>scm:jazz:https://rtc:9444/jazz:GPDBBuildWorkspace</connection>
    </scm>

Results in the implementation of MVN Release:prepare, after the discovery of the tag SCM, pom.xml inside the connection into a

<scm>        <connection>scm:jazz:https://rtc:9444/jazz:gpdbbuildworkspace/jazz:tag-version</ Connection>
    </scm>

This is not seen in standard MAVEN project, and the standard SCM tag changes back to the previously configured amount workspace. The details of this question I did not study, see the official document after this sentence: it is very strongly recommended that a separate repository workspace, containing just one Componen T, the component to be released, is set up for exactly this purpose. Refactoring the project in the RTC structure to solve the problem. The file structure after resolution
Component5
Project1
Project 2
Project 3
Pom.xml
Settings.xml did not automatically push, this problem only occurs on my local machine, feel very strange. Looking at the SCM plugin code, found that the system platform encoding different causes, before the push will read the current baseline and workspace information comparison, with a simple string parse, did not consider the UTF problem, So only finally through the modification Scm.ini solves.

-duser.language=us-dfile.encoding= "UTF-8"

Push encounters Changset should be associate with artifact ID, this problem can be referred to scm775 and MRELEASE-909, this problem has been resolved, Unfortunately, Chris submitted a code that missed the SCM-related release and now doesn't see any sign of Chris Release, and there's no way to get the relevant GIT code locally, create your own local version, put releases plugin and SCM Plugin is placed in the local repo.
Release plugin version customization:
A. Download the current version of the ZIP package in git version of release plugin
B. Merging the release-related code from Chris to the ZIP package version
C. Get the corresponding release package in the target folder with Mvn:install-dskiptests=true
SCM Plugin Version customization:
A. Download the version 1.9.4 Zip Package in the git version of SCM plugin
B. Merging the code that Chris changed into the ZIP package version
C. Get the corresponding release package in the target folder with Mvn:install-dskiptests=true
In Settings.xml, create your own local plugin repo, put the customized version of the SCM plugin and release plugin under Project source control, and place the local plugin Repo point to the custom version of SCM and release plugin, done.