[
https://issues.apache.org/jira/browse/SCM-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961328#comment-17961328
]
ASF GitHub Bot commented on SCM-413:
------------------------------------
jira-importer commented on issue #621:
URL: https://github.com/apache/maven-scm/issues/621#issuecomment-2964607271
**[Michael
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
commented
This issue has been auto closed because it has been inactive for a long
period of time. If you think this issue still applies, retest your problem with
the most recent version of Maven and the affected component, reopen and post
your results.
> scm:bootstrap example needs updating or a warning associated with it
> --------------------------------------------------------------------
>
> Key: SCM-413
> URL: https://issues.apache.org/jira/browse/SCM-413
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 1.1
> Environment: Documentation
> Reporter: Andy Stocks
> Priority: Minor
>
> The scm:bootstrap example (
> http://maven.apache.org/scm/plugins/examples/bootstrapping-with-pom.html )
> shows how to use a pom file and maven to set up a project from scratch,
> pulling source code from a repository. What it doesn't mention is a situation
> that can occur once the code is checked out and the operation has finished.
> The bootstrap pom file remains - should you accidentally run an mvn clean
> with this pom (as the example shows) it will remove all the source code that
> has been checked out via the scm:bootstrap command. Unfortunately, this may
> be done by accident after many local changes have been made to the checked
> out source - losing all the changes not checked in. I think *it should be
> made very clear* in the example of this issue (or the example should be
> modified to either recommend removal of the bootstrap pom, or if it's
> possible include some mark-up to disable the clean operation (is this
> possible?)). This has made the case for using Maven more difficult to
> annoyed team members, in one case losing several days of work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
