Overview

Artifactory can exposes Maven indexes for use by Maven integrations of common IDEs (IntelliJ IDEA, NetBeans, Eclipse).

Artifactory's search and indexing facilities are not related to Maven indexes
The indexing done by Artifactory is secure, immediately effective and supports a larger variatiy of search options, including custom metadata searches. Maven indexes exist in Artifactory for the purpose IDE integrations only, and are calculated periodically, contain a limited set of data and are non-secure by design. Information about the content of a repository is exposed to anyone having access to the repository's index, regardless of any effective path permission you have in place. If that's a concern, do not expose an index for that repository.

Indexes are fetched remotely for remote repositories that provide them (many do not, or do not keep an updated index) and are calculated for local and virtual repositories.
If Artifactory cannot find a remote index, it will calculate one locally, based on the remote repository's already cached artifacts.

Usage

To administer Maven indexes go to Admin:Services:Indexer.
You can control how often local indexing calculation and remote index fetching will run and what repositories will be included in index calculation.

Indexing can be expensive
Please note that calculating and index for a repository may be a resource hungry operation, especially for a large local repository or if the repository is a virtual one, containing other underlying repositories. Therefore, do not include repositories you do not need indexing for in the period index calculation.

Exposing Maven Indexes

Overview

Usage