This is an automated email from the ASF dual-hosted git repository.
elharo 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 bb9d7d1f Remove obsolete info (#666)
bb9d7d1f is described below
commit bb9d7d1f498baf8f6e3d26f72582a39e120b750e
Author: Elliotte Rusty Harold <[email protected]>
AuthorDate: Thu Feb 6 11:00:07 2025 +0000
Remove obsolete info (#666)
---
.../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 5252da86..966ee557 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
