git - Maven-Release-Plugin: Force to use specific version of scm provider -

I am trying to migrate our repository from the SIVN to the grip and I'm having trouble in the release plugin, a lot On the big project

Problem:

There are about 50+ sub-modules in this project and it attempts to add all modified pomas into a 'GIT add'. . This window breaks the command line limit.

Fortunately, a fix was placed for it in 1.8.1 maven-scm-provider-gitexe although the maven-release-plugin is currently set to use 1.7 which is not good enough.

I have tried to add the following to my root pom.xml but I can still download it during the 1.7 mvn release: Process is also being processed in Verbose mode Not indicating that it is using 1.8.1.

  & lt; Plugin & gt; & Lt; Group & gt; Org.apache.maven.plugins & lt; / Group & gt; & Lt; ArtifactId & gt; Maven release-plugin & lt; / ArtifactId> & Lt; Version & gt; 2.3.2 & lt; / Edition & gt; & Lt; Hanging & gt; & Lt; Execution & gt; & Lt; ID & gt; Default & lt; / Id & gt; & Lt; Goals & gt; & Lt; Goal & gt; Display & lt; / Target & gt; & Lt; / Targets & gt; & Lt; Configuration & gt; & Lt; PomFileName & gt; Subproj / pom.xml & lt; / PomFileName & gt; & Lt; / Configuration & gt; & Lt; / Execution & gt; & Lt; / Hanging & gt; & Lt; Dependency & gt; & Lt; Dependency & gt; & Lt; Group & gt; Org.apache.maven.scm & lt; / Group & gt; & Lt; ArtifactId & gt; Maven-SCM-api & lt; / ArtifactId> & Lt; Version & gt; 1.8.1 & lt; / Edition & gt; & Lt; / Dependencies & gt; & Lt; Dependency & gt; & Lt; Group & gt; Org.apache.maven.scm & lt; / Group & gt; & Lt; ArtifactId & gt; Maven-SCM-Provider- gitexe & lt; / ArtifactId> & Lt; Version & gt; 1.8.1 & lt; / Edition & gt; & Lt; / Dependencies & gt; & Lt; / Dependencies & gt; & Lt; / Plugin & gt;   
 I have also tried to add the pom.xml to the following, which attempts to force it to use it with the more fate to use the correct version.  
  & lt; Extensions & gt; & Lt; Expansion & gt; & Lt; Group & gt; Org.apache.maven.scm & lt; / Group & gt; & Lt; ArtifactId & gt; Maven-SCM-Provider- gitexe & lt; / ArtifactId> & Lt; Version & gt; 1.8.1 & lt; / Edition & gt; & Lt; / Extension & gt; & Lt; / Extensions & gt;   
 The reason I suspect is that it is not using 1.8.1 is that it still fails to try adding a git with all the palm files, while I plug in The source code has been checked which surely looks like it should add each file separately to Windows (CodeHouse Pelices DOS.ISFAMili (OSFAMI_Windows) also to ensure that I am returning true to my machine. Go twice  
 What am I missing? How can I apply the Release plugin to use the correct version of the SMM plugin?   
 
 
 
 Therefore you should try version 2.4. It should work and you will probably not be affected by the bug.  
 This future Wait for the version of ...   
 Edit: The bug is related to this SCM bug:  
 To use a comment  maven-scm -provider-gitexe  and  maven-scm-provider-git-commons  as a dependency  
  & lt; Dependency & gt; & Lt; Dependency & gt; & Lt; Group & gt; Org.apache.maven.scm & lt; / Group & gt; & Lt; ArtifactId & gt; Maven-SCM-Provider- gitexe & lt; / ArtifactId> & Lt; Version & gt; 1.8.1 & lt; / Edition & gt; & Lt; / Dependencies & gt; & Lt; Dependency & gt; & Lt; Group & gt; Org.apache.maven.scm & lt; / Group & gt; & Lt; ArtifactId & gt; Maven-SCM-Provider- Git-Commons & lt; / ArtifactId> & Lt; Version & gt; 1.8.1 & lt; / Edition & gt; & Lt; / Dependencies & gt; & Lt; / Dependencies & gt;