public final class ResourceDecorationContributorTestSupport
extends java.lang.Object
| Constructor and Description |
|---|
ResourceDecorationContributorTestSupport() |
| Modifier and Type | Method and Description |
|---|---|
static <T extends net.nemerosa.ontrack.model.structure.ProjectEntity> |
createResourceObjectMapper(java.lang.Class<T> type,
net.nemerosa.ontrack.ui.resource.ResourceDecorationContributor<T> contributor,
net.nemerosa.ontrack.model.security.SecurityService securityService)
The BuildResourceDecorator is NOT loaded since it belongs to the "ui" module.
|
public ResourceDecorationContributorTestSupport()
public static <T extends net.nemerosa.ontrack.model.structure.ProjectEntity> net.nemerosa.ontrack.ui.resource.ResourceObjectMapper createResourceObjectMapper(java.lang.Class<T> type,
net.nemerosa.ontrack.ui.resource.ResourceDecorationContributor<T> contributor,
net.nemerosa.ontrack.model.security.SecurityService securityService)
See if core resource decorators could be put in a separate module. They cannot because they themselves rely on the UI controllers.
So, in order to test a resource decoration contributor in an extension, we'd have to load the complete UI module, which is not very practical.
We can, on the other hand, create a fake resource decorator to wrap the resource decoration contributor to test.