JaVers restores commit-deep shadow graph. Referenced
objects are resolved if they exist in selected commits.
Caution! Commit-deep doesn't mean full.
References to objects that aren't available in selected commits are nulled.
This may be observed as unexpected gaps in a shadow graph.
You can fill these gaps using Commit-deep+ scope.
Commit-deep query is slower than shallow query,
because JaVers executes the additional query to load all
snapshots in commits touched by the main JQL query.
JaVers tries to restore an original object graph
with (possibly) all object references resolved.
Caution! Commit-deep+ doesn't mean full, it just
fills recursively potential gaps in the restored object graph.
We have to stop somewhere. The query parameter maxGapsToFill
limits the number of objects that would be loaded.
Think of commit-deep+ scope as commit-deep with up to N gaps filled.
Commit-deep+ query is slower than commit-deep query.
JaVers executes up to N additional queries to fill potential gaps in the object graph created by the commit-deep query
(one query per each gap).
Returns an array containing the constants of this enum type, in
the order they are declared. This method may be used to iterate
over the constants as follows:
for (ShadowScope c : ShadowScope.values())
an array containing the constants of this enum type, in the order they are declared
public static ShadowScope valueOf(java.lang.String name)
Returns the enum constant of this type with the specified name.
The string must match exactly an identifier used to declare an
enum constant in this type. (Extraneous whitespace characters are
name - the name of the enum constant to be returned.
the enum constant with the specified name
java.lang.IllegalArgumentException - if this enum type has no constant with the specified name
java.lang.NullPointerException - if the argument is null