1.0.0 Root element of the user configuration file. 1.0.0 Root element of the user configuration file. 1.0.0 The local repository. 1.0.0 Whether Maven should attempt to interact with the user for input. 1.0.0 Whether Maven should use the plugin-registry.xml file to manage plugin versions. 1.0.0 Indicate whether maven should operate in offline mode full-time. 1.0.0 Configuration for different proxy profiles. Multiple proxy profiles might come in handy for anyone working from a notebook or other mobile platform, to enable easy switching of entire proxy configurations by simply specifying the profile id, again either from the command line or from the defaults section below. 1.0.0 Configuration of server-specific settings, mainly authentication method. This allows configuration of authentication on a per-server basis. 1.0.0 Configuration of download mirrors for repositories. 1.0.0 Configuration of build profiles for adjusting the build according to environmental parameters 1.0.0 List of manually-activated build profiles, specified in the order in which they should be applied. 1.0.0 List of groupIds to search for a plugin when that plugin groupId is not explicitly provided. 1.0.0 A download mirror for a given repository. 1.0.0 The server ID of the repository being mirrored, eg "central". This MUST NOT match the mirror id. 1.0.0 The optional name that describes the mirror. 1.0.0 The URL of the mirror repository. 1.0.0 1.0.0 1.0.0 Whether this proxy configuration is the active one. 1.0.0 The proxy protocol. 1.0.0 The proxy user. 1.0.0 The proxy password. 1.0.0 The proxy port. 1.0.0 The proxy host. 1.0.0 The list of non-proxied hosts (usually comma-delimited). 1.0.0 1.0.0 1.0.0 The username used to authenticate. 1.0.0 The password used in conjunction with the username to authenticate. 1.0.0 The private key location used to authenticate. 1.0.0 The passphrase used in conjunction with the privateKey to authenticate. 1.0.0 The permissions for files when they are created. 1.0.0 The permissions for directories when they are created. 0.0.0+ Extra configuration for the transport layer. 1.0.0 1.0.0 Modifications to the build process which is keyed on some sort of environmental parameter. 1.0.0 The conditional logic which will automatically trigger the inclusion of this profile. 0.0.0+ Extended configuration specific to this profile goes here. Contents take the form of <property.name>property.value</property.name> 1.0.0 The lists of the remote repositories 1.0.0 The lists of the remote repositories for discovering plugins 1.0.0 1.0.0 Repository contains the information needed for establishing connections with remote repoistory 1.0.0 How to handle downloading of releases from this repository 1.0.0 How to handle downloading of snapshots from this repository 1.0.0 A unique identifier for a repository. 1.0.0 Human readable name of the repository 1.0.0 The url of the repository 1.0.0 The type of layout this repository uses for locating and storing artifacts - can be "legacy" or "default". 1.0.0 Download policy 1.0.0 Whether to use this repository for downloading this type of artifact 1.0.0 The frequency for downloading updates - can be "always", "daily" (default), "interval:XXX" (in minutes) or "never" (only if it doesn't exist locally). 1.0.0 What to do when verification of an artifact checksum fails - warn, fail, etc. Valid values are "fail" or "warn" 1.0.0 The conditions within the build runtime environment which will trigger the automatic inclusion of the parent build profile. 1.0.0 Flag specifying whether this profile is active as a default. 1.0.0 Specifies that this profile will be activated when a matching JDK is detected. 1.0.0 Specifies that this profile will be activated when matching OS attributes are detected. 1.0.0 Specifies that this profile will be activated when this System property is specified. 1.0.0 Specifies that this profile will be activated based on existence of a file. 1.0.0 This is the file specification used to activate a profile. The missing value will be a the location of a file that needs to exist, and if it doesn't the profile must run. On the other hand exists will test for the existence of the file and if it is there will run the profile. 1.0.0 The name of the file that should be missing to activate a profile 1.0.0 The name of the file that should exist to activate a profile 1.0.0 This is an activator which will detect an operating system's attributes in order to activate its profile. 1.0.0 The name of the OS to be used to activate a profile 1.0.0 The general family of the OS to be used to activate a profile (e.g. 'windows') 1.0.0 The architecture of the OS to be used to activate a profile 1.0.0 The version of the OS to be used to activate a profile 1.0.0 This is the property specification used to activate a profile. If the value field is empty, then the existence of the named property will activate the profile, otherwise it does a case-sensitive match against the property value as well. 1.0.0 The name of the property to be used to activate a profile 1.0.0 The value of the property to be used to activate a profile