Package org.eclipse.aether
Class ConfigurationProperties
java.lang.Object
org.eclipse.aether.ConfigurationProperties
The keys and defaults for common configuration properties.
- See Also:
- 
Field SummaryFieldsModifier and TypeFieldDescriptionstatic final StringThe maximum amount of time (in milliseconds) to wait for a successful connection to a remote server.static final intThe default connect timeout to use ifCONNECT_TIMEOUTisn't set.static final booleanThe default HTTP redirect mode ifHTTP_FOLLOW_REDIRECTSisn't set.static final intThe default value to use ifHTTP_CONNECTION_MAX_TTLisn't set (300 seconds).static final StringThe default encoding/charset to use ifHTTP_CREDENTIAL_ENCODINGisn't set.static final intThe default value to use ifHTTP_MAX_CONNECTIONS_PER_ROUTEisn't set (50 connections).static final intThe default max redirect count to follow for the HTTP transport.static final booleanThe default value to use ifHTTP_PREEMPTIVE_AUTHisn't set (false).static final intThe default number of retries to use ifHTTP_RETRY_HANDLER_COUNTisn't set.static final longThe default initial retry interval to use ifHTTP_RETRY_HANDLER_INTERVALisn't set.static final longThe default retry interval maximum to use ifHTTP_RETRY_HANDLER_INTERVAL_MAXisn't set.static final StringThe default HTTP codes of remote server responses that should be handled as "too many requests".static final booleanThe default value to use ifHTTP_REUSE_CONNECTIONSisn't set (true).static final booleanThe default extension priority mode ifIMPLICIT_PRIORITIESisn't set.static final booleanThe default interactive mode ifINTERACTIVEisn't set.static final booleanThe default checksum persistence mode ifPERSISTED_CHECKSUMSisn't set.static final intThe default request timeout to use ifREQUEST_TIMEOUTisn't set.static final StringThe default user agent to use ifUSER_AGENTisn't set.static final StringTotal time to live in seconds for an HTTP connection, after that time, the connection will be dropped (no matter for how long it was idle).static final StringThe encoding/charset to use when exchanging credentials with HTTP servers.static final StringBoolean flag should the HTTP transport use expect-continue handshake for PUT requests.static final StringIf enabled, the HTTP transport will follow HTTP redirects.static final StringThe request headers to use for HTTP-based repository connectors.static final StringThe maximum concurrent connections per route HTTP client is allowed to use.static final StringThe max redirect count to follow for the HTTP transport.static final StringShould HTTP client use preemptive auth (w/ BASIC) or not?static final StringThe maximum number of times a request to a remote server should be retried in case of an error.static final StringThe initial retry interval of request to a remote server should be waited in case of "too many requests" (HTTP codes 429 and 503).static final StringThe maximum retry interval of request to a remote server above which the request should be aborted instead.static final StringThe HTTP codes of remote server responses that should be handled as "too many requests" (examples: HTTP codes 429 and 503).static final StringShould HTTP client reuse connections (in other words, pool connections) or not?static final StringThe mode that sets HTTPS transport "security mode": to ignore any SSL errors (certificate validity checks, hostname verification).static final StringThe default HTTPS security mode.static final StringThe insecure HTTPS security mode (certificate validation, hostname verification are all ignored).static final StringA flag indicating whether the priorities of pluggable extensions are implicitly given by their iteration order such that the first extension has the highest priority.static final StringA flag indicating whether interaction with the user is allowed.static final StringA flag indicating whether checksums which are retrieved during checksum validation should be persisted in the local filesystem next to the file they provide the checksum for.static final StringThe prefix for properties that control the priority of pluggable extensions like transporters.static final StringThe maximum amount of time (in milliseconds) to wait for remaining data to arrive from a remote server.static final StringThe user agent that repository connectors should report to servers.
- 
Method Summary
- 
Field Details- 
PREFIX_PRIORITYThe prefix for properties that control the priority of pluggable extensions like transporters. For example, for an extension with the fully qualified class name "org.eclipse.MyExtensionFactory", the configuration properties "aether.priority.org.eclipse.MyExtensionFactory", "aether.priority.MyExtensionFactory" and "aether.priority.MyExtension" will be consulted for the priority, in that order (obviously, the last key is only tried if the class name ends with "Factory"). The corresponding value is a float and the special valueFloat.NaNor "NaN" (case-sensitive) can be used to disable the extension.- See Also:
 
- 
IMPLICIT_PRIORITIESA flag indicating whether the priorities of pluggable extensions are implicitly given by their iteration order such that the first extension has the highest priority. If set, an extension's built-in priority as well as any correspondingaether.priority.*configuration properties are ignored when searching for a suitable implementation among the available extensions. This priority mode is meant for cases where the application will present/inject extensions in the desired search order.- See Also:
 
- 
DEFAULT_IMPLICIT_PRIORITIESThe default extension priority mode ifIMPLICIT_PRIORITIESisn't set.- See Also:
 
- 
INTERACTIVEA flag indicating whether interaction with the user is allowed.- See Also:
 
- 
DEFAULT_INTERACTIVEThe default interactive mode ifINTERACTIVEisn't set.- See Also:
 
- 
USER_AGENTThe user agent that repository connectors should report to servers.- See Also:
 
- 
DEFAULT_USER_AGENTThe default user agent to use ifUSER_AGENTisn't set.- See Also:
 
- 
CONNECT_TIMEOUTThe maximum amount of time (in milliseconds) to wait for a successful connection to a remote server. Non-positive values indicate no timeout.- See Also:
 
- 
DEFAULT_CONNECT_TIMEOUTThe default connect timeout to use ifCONNECT_TIMEOUTisn't set.- See Also:
 
- 
REQUEST_TIMEOUTThe maximum amount of time (in milliseconds) to wait for remaining data to arrive from a remote server. Note that this timeout does not restrict the overall duration of a request, it only restricts the duration of inactivity between consecutive data packets. Non-positive values indicate no timeout.- See Also:
 
- 
DEFAULT_REQUEST_TIMEOUTThe default request timeout to use ifREQUEST_TIMEOUTisn't set.- See Also:
 
- 
HTTP_HEADERSThe request headers to use for HTTP-based repository connectors. The headers are specified using aMap<String, String>, mapping a header name to its value. Besides this general key, clients may also specify headers for a specific remote repository by appending the suffix.<repoId>to this key when storing the headers map. The repository-specific headers map is supposed to be complete, i.e. is not merged with the general headers map.- See Also:
 
- 
HTTP_CREDENTIAL_ENCODINGThe encoding/charset to use when exchanging credentials with HTTP servers. Besides this general key, clients may also specify the encoding for a specific remote repository by appending the suffix.<repoId>to this key when storing the charset name.- See Also:
 
- 
DEFAULT_HTTP_CREDENTIAL_ENCODINGThe default encoding/charset to use ifHTTP_CREDENTIAL_ENCODINGisn't set.- See Also:
 
- 
HTTP_RETRY_HANDLER_COUNTThe maximum number of times a request to a remote server should be retried in case of an error.- Since:
- 1.9.6
- See Also:
 
- 
DEFAULT_HTTP_RETRY_HANDLER_COUNTThe default number of retries to use ifHTTP_RETRY_HANDLER_COUNTisn't set.- Since:
- 1.9.6
- See Also:
 
- 
HTTP_RETRY_HANDLER_INTERVALThe initial retry interval of request to a remote server should be waited in case of "too many requests" (HTTP codes 429 and 503). Accepts long as milliseconds. This value is used if remote server does not useRetry-Afterheader, in which case Server value is obeyed.- Since:
- 1.9.16
- See Also:
 
- 
DEFAULT_HTTP_RETRY_HANDLER_INTERVALThe default initial retry interval to use ifHTTP_RETRY_HANDLER_INTERVALisn't set. Default value 5000ms.- Since:
- 1.9.16
- See Also:
 
- 
HTTP_RETRY_HANDLER_INTERVAL_MAXThe maximum retry interval of request to a remote server above which the request should be aborted instead. In theory, a malicious server could tell Maven "come back after 100 years" that would stall the build for some. Using this parameter Maven will fail the request instead, if interval is above this value.- Since:
- 1.9.16
- See Also:
 
- 
DEFAULT_HTTP_RETRY_HANDLER_INTERVAL_MAXThe default retry interval maximum to use ifHTTP_RETRY_HANDLER_INTERVAL_MAXisn't set. Default value 5 minutes.- Since:
- 1.9.16
- See Also:
 
- 
HTTP_RETRY_HANDLER_SERVICE_UNAVAILABLEThe HTTP codes of remote server responses that should be handled as "too many requests" (examples: HTTP codes 429 and 503). Accepts comma separated list of HTTP response codes.- Since:
- 1.9.16
- See Also:
 
- 
DEFAULT_HTTP_RETRY_HANDLER_SERVICE_UNAVAILABLEThe default HTTP codes of remote server responses that should be handled as "too many requests". Default value: "429,503".- Since:
- 1.9.16
- See Also:
 
- 
HTTP_PREEMPTIVE_AUTHShould HTTP client use preemptive auth (w/ BASIC) or not?- Since:
- 1.9.6
- See Also:
 
- 
DEFAULT_HTTP_PREEMPTIVE_AUTHThe default value to use ifHTTP_PREEMPTIVE_AUTHisn't set (false).- Since:
- 1.9.6
- See Also:
 
- 
HTTP_REUSE_CONNECTIONSShould HTTP client reuse connections (in other words, pool connections) or not?- Since:
- 1.9.8
- See Also:
 
- 
DEFAULT_HTTP_REUSE_CONNECTIONSThe default value to use ifHTTP_REUSE_CONNECTIONSisn't set (true).- Since:
- 1.9.8
- See Also:
 
- 
HTTP_CONNECTION_MAX_TTLTotal time to live in seconds for an HTTP connection, after that time, the connection will be dropped (no matter for how long it was idle).- Since:
- 1.9.8
- See Also:
 
- 
DEFAULT_HTTP_CONNECTION_MAX_TTLThe default value to use ifHTTP_CONNECTION_MAX_TTLisn't set (300 seconds).- Since:
- 1.9.8
- See Also:
 
- 
HTTP_MAX_CONNECTIONS_PER_ROUTEThe maximum concurrent connections per route HTTP client is allowed to use.- Since:
- 1.9.8
- See Also:
 
- 
DEFAULT_HTTP_MAX_CONNECTIONS_PER_ROUTEThe default value to use ifHTTP_MAX_CONNECTIONS_PER_ROUTEisn't set (50 connections).- Since:
- 1.9.8
- See Also:
 
- 
HTTP_EXPECT_CONTINUEBoolean flag should the HTTP transport use expect-continue handshake for PUT requests. Not all transport support this option. This option may be needed for some broken HTTP servers. Default value corresponds to given transport default one (resolver does not override those), but if configuration IS given, it will replace given transport own default value.- Since:
- 1.9.17
- See Also:
 
- 
HTTPS_SECURITY_MODEThe mode that sets HTTPS transport "security mode": to ignore any SSL errors (certificate validity checks, hostname verification). The default value isHTTPS_SECURITY_MODE_DEFAULT.- Since:
- 1.9.6
- See Also:
 
- 
HTTPS_SECURITY_MODE_DEFAULTThe default HTTPS security mode.- Since:
- 1.9.6
- See Also:
 
- 
HTTPS_SECURITY_MODE_INSECUREThe insecure HTTPS security mode (certificate validation, hostname verification are all ignored).- Since:
- 1.9.6
- See Also:
 
- 
PERSISTED_CHECKSUMSA flag indicating whether checksums which are retrieved during checksum validation should be persisted in the local filesystem next to the file they provide the checksum for.- See Also:
 
- 
DEFAULT_PERSISTED_CHECKSUMSThe default checksum persistence mode ifPERSISTED_CHECKSUMSisn't set.- See Also:
 
- 
HTTP_FOLLOW_REDIRECTSIf enabled, the HTTP transport will follow HTTP redirects.- Since:
- 1.9.23
- See Also:
 
- 
DEFAULT_FOLLOW_REDIRECTSThe default HTTP redirect mode ifHTTP_FOLLOW_REDIRECTSisn't set.- Since:
- 1.9.23
- See Also:
 
- 
HTTP_MAX_REDIRECTSThe max redirect count to follow for the HTTP transport.- Since:
- 1.9.23
- See Also:
 
- 
DEFAULT_HTTP_MAX_REDIRECTSThe default max redirect count to follow for the HTTP transport.- Since:
- 1.9.23
- See Also:
 
 
-