public interface RepositoryConnector extends Closeable
If applicable, a connector should obey connect/request timeouts and other relevant settings from the
configuration properties of the repository
session it has been obtained for. However, a connector must not emit any events to the transfer listener configured
for the session. Instead, transfer events must be emitted only to the listener (if any) specified for a given
Note: While a connector itself can use multiple threads internally to performs the transfers, clients must not call a connector concurrently, i.e. connectors are generally not thread-safe.
|Modifier and Type||Method and Description|
Closes this connector and frees any network resources associated with it.
Performs the specified downloads.
Performs the specified uploads.
void get(Collection<? extends ArtifactDownload> artifactDownloads, Collection<? extends MetadataDownload> metadataDownloads)
MetadataTransfer.getException(), respectively. If reasonable, a connector should continue to process the remaining downloads after an error to retrieve as many items as possible. The connector may perform the transfers concurrently and in any order.
artifactDownloads- The artifact downloads to perform, may be
metadataDownloads- The metadata downloads to perform, may be
void put(Collection<? extends ArtifactUpload> artifactUploads, Collection<? extends MetadataUpload> metadataUploads)
MetadataTransfer.getException(), respectively. The connector may perform the transfers concurrently and in any order.
artifactUploads- The artifact uploads to perform, may be
metadataUploads- The metadata uploads to perform, may be
IllegalStateExceptionor similar. Closing an already closed connector is harmless and has no effect.
Copyright © 2010–2022 The Apache Software Foundation. All rights reserved.