To model a module in your dependency declarations. Usually you can either declare a single dependency artifact or you declare a module dependency that depends on a module descriptor in a repository. With a client module you can declare a module dependency without the need of a module descriptor in a remote repository.
| Fields inherited from class | Fields |
|---|---|
interface Dependency |
ARCHIVES_CONFIGURATION, CLASSIFIER, DEFAULT_CONFIGURATION |
| Type | Name and description |
|---|---|
void |
addDependency(ModuleDependency dependency)Add a dependency to the client module. |
ClientModule |
copy(){@inheritDoc} |
Set<ModuleDependency> |
getDependencies()Returns all the dependencies added to the client module. |
String |
getId()Returns the id of the client module. |
| Methods inherited from class | Name |
|---|---|
interface ExternalModuleDependency |
copy, isChanging, setChanging |
interface ExternalDependency |
copy, isForce, setForce |
interface ModuleVersionSelector |
getGroup, getName, getVersion, matchesStrictly |
interface ModuleDependency |
addArtifact, artifact, copy, exclude, getArtifacts, getConfiguration, getExcludeRules, isTransitive, setTransitive |
interface Dependency |
contentEquals, copy, getGroup, getName, getVersion |
Add a dependency to the client module. Such a dependency is transitive dependency for the project that has a dependency on the client module.
dependency - The dependency to add to the client module.{@inheritDoc}
Returns all the dependencies added to the client module.
Returns the id of the client module. This is usually only used for internal handling of the client module.