(maven-site) branch elharo-patch-5 created (now a5779bb2)

[el...@apache.org]

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

elharo pushed a change to branch elharo-patch-5
in repository https://gitbox.apache.org/repos/asf/maven-site.git


      at a5779bb2 Remove obsolete info

This branch includes the following new commits:

     new a5779bb2 Remove obsolete info

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

(maven-site) 01/01: Remove obsolete info

[el...@apache.org]

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

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

commit a5779bb279698821eabc448e6b5c0a982f7a84a6
Author: Elliotte Rusty Harold <el...@users.noreply.github.com>
AuthorDate: Wed Feb 5 20:24:08 2025 +0000

    Remove obsolete info
---
 .../guides/introduction/introduction-to-repositories.apt | 16 ++++++----------
 1 file changed, 6 insertions(+), 10 deletions(-)

diff --git a/content/apt/guides/introduction/introduction-to-repositories.apt b/content/apt/guides/introduction/introduction-to-repositories.apt
index 099abbdc..420a9a4f 100644
--- a/content/apt/guides/introduction/introduction-to-repositories.apt
+++ b/content/apt/guides/introduction/introduction-to-repositories.apt
@@ -117,22 +117,18 @@ Introduction to Repositories
 
 * Setting up the Internal Repository
 
- To set up an internal repository just requires that you have a place to put it, and then copy
+ Setting up an internal repository just requires that you have a place to put it, and then copy
  required artifacts there using the same layout as in a remote repository such as {{{https://repo.maven.apache.org/maven2/}repo.maven.apache.org}}.
 
- It is <not> recommended that you scrape or <<<rsync://>>> a full copy of central as there is a large amount
+ Do <not> scrape or <<<rsync://>>> a full copy of central as there is a large amount
  of data there and doing so will get you banned. You can use a program such as those described on the {{{../../repository-management.html}Repository Management}} page to
  run your internal repository's server, download from the internet as required, and then hold
  the artifacts in your internal repository for faster downloading later.
 
- The other options available are to manually download and vet releases, then copy them to the internal
- repository, or to have Maven download them for a user, and manually upload the vetted artifacts to the
- internal repository which is used for releases. This step is the only one available for artifacts where
- the license forbids their distribution automatically, such as several J2EE JARs provided by Sun.
- Refer to the {{{../mini/guide-coping-with-sun-jars.html}Guide to coping with SUN JARs}} document for more information.
-
- It should be noted that Maven intends to include enhanced support for such features in the future,
- including click through licenses on downloading, and verification of signatures.
+ The other options are to manually download and vet releases, then copy them to the internal
+ repository; or to have Maven download them for a user, then manually upload the vetted artifacts to the
+ internal repository which is used for releases. This step is useful for artifacts whose
+ license forbids their automatic distribution, such as several J2EE JARs.
 
 * Using the Internal Repository