Package org.eclipse.aether.internal.impl.synccontext.named

Class BasedirNameMapper

java.lang.Object

org.eclipse.aether.internal.impl.synccontext.named.BasedirNameMapper

All Implemented Interfaces:

NameMapper

public class BasedirNameMapper
extends Object
implements NameMapper

Wrapping NameMapper class that is file system friendly: it wraps another NameMapper and resolves the resulting "file system friendly" names against local repository basedir.

Since:

1.9.0

Constructor Summary

Constructors

Constructor	Description
BasedirNameMapper(NameMapper delegate)

Method Summary

Modifier and Type	Method	Description
boolean	isFileSystemFriendly()	Returns true if lock names returned by this lock name mapper are file system friendly, can be used as file names and paths.
Collection<String>	nameLocks(RepositorySystemSession session, Collection<? extends Artifact> artifacts, Collection<? extends Metadata> metadatas)	Creates (opaque) names for passed in artifacts and metadata.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

BasedirNameMapper

public BasedirNameMapper(NameMapper delegate)

Method Details

isFileSystemFriendly

public boolean isFileSystemFriendly()

Description copied from interface: NameMapper

Returns true if lock names returned by this lock name mapper are file system friendly, can be used as file names and paths.

Specified by:

isFileSystemFriendly in interface NameMapper

nameLocks

public Collection<String> nameLocks(RepositorySystemSession session,
 Collection<? extends Artifact> artifacts,
 Collection<? extends Metadata> metadatas)

Description copied from interface: NameMapper

Creates (opaque) names for passed in artifacts and metadata. Returned collection has max size of sum of the passed in artifacts and metadata collections, or less. If an empty collection is returned, there will be no locking happening. Never returns null. The resulting collection MUST BE "stable" (always sorted by same criteria) to avoid deadlocks by acquiring locks in same order, essentially disregarding the order of the input collections.

There is no requirement of any kind of "parity" between input element count (sum of two collections, that is) and output collection size, just the returned upper size limit is defined (sum of the passed in two collections size). If returned collection is empty, no locking will happen, if single element, one lock will be used, if two then two named locks will be used etc.

Specified by:

nameLocks in interface NameMapper