[
https://issues.apache.org/jira/browse/SCM-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962730#comment-17962730
]
ASF GitHub Bot commented on SCM-714:
------------------------------------
jira-importer commented on issue #928:
URL: https://github.com/apache/maven-scm/issues/928#issuecomment-2964633504
**[Mark
Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)**
commented
Hi Felix!
Please note that scm:add != git-add and scm:checkin != git-commit
maven-scm is intended to work the same way on every SCM. Thus we 'mimic' svn
and cvs like operations.
In the maven-release-manager we already do some special things for GIT. We'd
need to
There is of course an option to move the 'splitting' of git-add to an own
function internally and utilize this from the other operations which need it.
> mvn release:prepare fails if the command line is too long on windows
> --------------------------------------------------------------------
>
> Key: SCM-714
> URL: https://issues.apache.org/jira/browse/SCM-714
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.8.1
> Reporter: Felix Simmendinger
> Assignee: Robert Scholte
> Priority: Blocker
>
> The issue from SCM-697 does not solve the issue as the gitprovider is not
> using the add command but the checkin command during a release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
