[
https://issues.apache.org/jira/browse/MRELEASE-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533311#comment-17533311
]
Hudson commented on MRELEASE-1082:
----------------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven-release » master #25
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-release/job/master/25/
> Add configuration option for shallow checkout/clone
> ---------------------------------------------------
>
> Key: MRELEASE-1082
> URL: https://issues.apache.org/jira/browse/MRELEASE-1082
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: scm
> Affects Versions: 3.0.0-M5
> Reporter: Michael Cramer
> Assignee: Michael Osipov
> Priority: Major
> Labels: checkout, clone, git, shallow, up-for-grabs
> Fix For: 3.0.0-M6
>
>
> after implementing sonar into our release process we noticed that sonar is
> complaining about missing blame information
> {noformat}
> [INFO] [WARNING] Missing blame information for the following files:
> {noformat}
> I've seen that in MRELEASE-993 this new type of checkout was introduced and
> it mentions that "per default" the checkout will use the shallow clone. to
> me, it sounds that this is an option that can be configured, but after taking
> a look in the code I see that {{true}} is hardcoded
> i would propose to make this option configurable and have a default of
> {{true}} that can be changed when needed, e.g. in the case during the release
> sonarqube is called which needs the full history.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
