public class StaticNameMapper extends java.lang.Object implements NameMapper
NameMapper
, always assigns one same name, effectively becoming equivalent to "static" sync context:
always maps ANY input to same name.Constructor and Description |
---|
StaticNameMapper() |
Modifier and Type | Method and 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. |
java.util.Collection<java.lang.String> |
nameLocks(RepositorySystemSession session,
java.util.Collection<? extends Artifact> artifacts,
java.util.Collection<? extends Metadata> metadatas)
Creates (opaque) names for passed in artifacts and metadata.
|
public boolean isFileSystemFriendly()
NameMapper
true
if lock names returned by this lock name mapper are file system friendly, can be used
as file names and paths.isFileSystemFriendly
in interface NameMapper
public java.util.Collection<java.lang.String> nameLocks(RepositorySystemSession session, java.util.Collection<? extends Artifact> artifacts, java.util.Collection<? extends Metadata> metadatas)
NameMapper
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.
nameLocks
in interface NameMapper