These are the majority of artifacts that reside within central. The first are artifacts that are used as dependencies of other artifacts. Repositories are home to two major types of artifacts. Use this element to specify which if it is default or legacy. Maven 2 has a default layout for its repositories however, Maven 1.x had a different layout.

layout: In the above description of repositories, it was mentioned that they all follow a common layout.

Your options are to ignore, fail, or warn on missing or incorrect checksums.

checksumPolicy: When Maven deploys files to the repository, it also deploys corresponding checksum files.

The choices are: always, daily (default), interval:X (where X is an integer in minutes) or never. Maven will compare the local POM’s timestamp (stored in a repository’s maven-metadata file) to the remote.

updatePolicy: This element specifies how often updates should attempt to occur.

enabled: true or false for whether this repository is enabled for the respective type ( releases or snapshots).

For example, one may decide to enable only snapshot downloads, possibly for development purposes. With these two sets, a POM has the power to alter the policies for each type independent of the other within a single repository.

releases, snapshots: These are the policies for each type of artifact, Release or snapshot.

There are two locations where a settings.xml file may live:

These include values such as the local repository location, alternate remote repository servers, and authentication information.

The settings element in the settings.xml file contains elements used to define values which configure Maven execution in various ways, like the pom.xml, but should not be bundled to any specific project, or distributed to an audience.

Pom for windows 10