ProGet Documentation

Maven Feeds in ProGet

  • Last Modified: 2019-07-18

Maven feeds contain a maven2-compatible Maven artifact repository. Maven works a little differently than the other feed types.

Maven Specifics

Maven artifacts are not self-contained archives; instead, an artifact is more of a grouping of files with some associated metadata. Because of this distinction, Maven feeds do not support drop path imports.

Connectors are also slightly different in Maven than in most other feed types. As there is no universal standard for searching or listing from a remote Maven repository, ProGet uses a rather dated API that provides an index of all artifacts. A task in the ProGet service will periodically download that index and unpack it to a local Lucene database, and use that for searching the remote repository. For the public apache Maven repository, this can be a very resource-intensive operation, and if you do not need this searching capability, we recommend disabling this task in ProGet. Artifacts accessed directly by name do not need this index.

As of ProGet 5.1.0, Maven feeds support alternate package stores (AWS, Azure).

Authenticating to Maven Feeds

Authentication settings for the maven client is configured in your settings.xlm file. You can use the standard <username> and <password> elements to store a username/password for ProGet, or you can specify api as the username, and an API Keys as a password.

Is this documentation incorrect or incomplete? Help us by contributing!

This documentation is licensed under CC-BY-SA-4.0 and stored in GitHub.

Generated from commit 7dbbedf1 on master