[
https://issues.apache.org/jira/browse/SCM-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960672#comment-17960672
]
ASF GitHub Bot commented on SCM-201:
------------------------------------
jira-importer commented on issue #446:
URL: https://github.com/apache/maven-scm/issues/446#issuecomment-2964595021
**[Emmanuel
Venisse](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=evenisse)**
commented
why don't you run something like this in a script:
if checkoutdir don't exists
run scm:checkout
else
run scm:update (or nothing)
I'm not really sure of the interest of this new parameter.
> Option to ignore checkout when checkoutDirectory exists
> -------------------------------------------------------
>
> Key: SCM-201
> URL: https://issues.apache.org/jira/browse/SCM-201
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: maven-plugin
> Affects Versions: 1.0-beta-3
> Environment: xp, starteam
> Reporter: Dan Tran
> Assignee: Dan Tran
> Priority: Major
> Fix For: 1.0-beta-4
>
>
> I have a need to pull mulitple legacy source trees from various scm:url into
> my local directory and invoke antrun to work on those trees.
> So I use multiple executions of maven-scm-plugin:checkout to fetch the source
> at initialize phase, then invoke antrun to do the rest.
> The annoy thing for every build is that scm:checkout remove my source tree
> and then fetch the source. This is the behavior we want
> for normal case. However for my case the checkout is a lengthy process.
> I would like to propose a new optiontion param skipCheckoutIfExists, with
> default to false to checkout mojo.
> WDYT? skipCheckoutIfExists name sound acceptable?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
