[maven-site] branch master updated: remove section on CVS (#65)

[ol...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

olamy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new d0a989b  remove section on CVS (#65)
d0a989b is described below

commit d0a989b9e65673a5d95ef0040840b980e5a36ae5
Author: Elliotte Rusty Harold <el...@users.noreply.github.com>
AuthorDate: Thu Jan 24 16:35:28 2019 -0500

    remove section on CVS (#65)
    
    1. CVS is very rarely used any more
    2. Nothing said here is the primary reason. Generated artifacts don't belong in source repos for much more important reasons.
    3. In 2018 devs are much less likely to try this. Maven repos are the default assumption.
    
    If you don't agree the entire section can simply be deleted, I can try to write an alternate reason why jars don't belong in source control.
---
 .../introduction/introduction-to-repositories.apt  | 24 ----------------------
 1 file changed, 24 deletions(-)

diff --git a/content/apt/guides/introduction/introduction-to-repositories.apt b/content/apt/guides/introduction/introduction-to-repositories.apt
index 4125f91..6952b47 100644
--- a/content/apt/guides/introduction/introduction-to-repositories.apt
+++ b/content/apt/guides/introduction/introduction-to-repositories.apt
@@ -49,30 +49,6 @@ Introduction to Repositories
  side, or they can be synced for offline use. The layout of the repositories is completely
  transparent to the Maven user, however.
 
-* Why not Store JARs in CVS?
-
- It is not recommended that you store your JARs in CVS. Maven tries to
- promote the notion of a user local repository where JARs, or any
- project artifacts, can be stored and used for any number of builds.
- Many projects have dependencies such as XML parsers and standard utilities that
- are often replicated in typical builds. With Maven these standard utilities
- can be stored in your local repository and shared by any number of builds.
-
- This has the following advantages:
-
- * <<It uses less storage>> - while a repository is typically quite large, because each JAR is only kept
-   in the one place it is actually saving space, even though it may not seem that way
-
- * <<It makes checking out a project quicker>> - initial checkout, and to a small degree updating, a
-   project will be faster if there are no large binary files in CVS. While they may need to be downloaded
-   again afterwards anyway, this only happens once and may not be necessary for some common JARs already in
-   place.
-
- * <<No need for versioning>> - CVS and other source control systems are designed for versioning files,
-   but external dependencies typically don't change, or if they do their filename changes anyway to indicate the
-   new version. Storing these in CVS doesn't have any added benefit over keeping them in a local artifact cache.
-
-
 * Using Repositories
 
   In general, you should not need to do anything with the local repository on a regular basis, except clean