[
https://issues.apache.org/jira/browse/SCM-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960744#comment-17960744
]
ASF GitHub Bot commented on SCM-259:
------------------------------------
jira-importer commented on issue #461:
URL: https://github.com/apache/maven-scm/issues/461#issuecomment-2964597123
**[Emmanuel
Venisse](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=evenisse)**
commented
I added a new parameter in update mojo
> Running scm:changelog after scm:update should be made configurable
> ------------------------------------------------------------------
>
> Key: SCM-259
> URL: https://issues.apache.org/jira/browse/SCM-259
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: maven-scm-api
> Reporter: Jan Hoeve
> Assignee: Emmanuel Venisse
> Priority: Minor
> Fix For: 1.0-rc1
>
>
> I do have a environment with cruisecontrol as a buildserver and clearcase as
> SCM provider.
> One entire build loop takes half an hour to complete. This is because the
> scm:update command fires an changelog command to get the changed files.
> This changelog process takes about 20 minutes to complete. My clearcase view
> has some 8500 files in it.
> (note: changelog is fired without the startDate, bad for performance on
> clearcase).
> It would be very nice if there was an option i could pass to mvn scm:update
> which skips the changelog process.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
