public interface RepositoryStateChangesReporter extends CollectRepositoryChangesPolicy
ChangesConsumer
Modifier and Type | Method and Description |
---|---|
void |
collectChanges(VcsRoot fromRepository,
RepositoryStateData fromState,
VcsRoot toRepository,
RepositoryStateData toState,
CheckoutRules checkoutRules,
ChangesConsumer consumer)
This method is called by the system to collect changes between two states.
|
getCurrentState
void collectChanges(@Nullable VcsRoot fromRepository, @NotNull RepositoryStateData fromState, @NotNull VcsRoot toRepository, @NotNull RepositoryStateData toState, @NotNull CheckoutRules checkoutRules, @NotNull ChangesConsumer consumer) throws VcsException
VcsRoot
, RepositoryStateData
]. The from pair is formed by
[ fromRepository != null ? fromRepository : toRepository
, fromState
], the to pair is formed by
[ toRepository
, toState
]. fromRepository
is set to null
iff it is the same as toRepository
.
fromRepository
is mainly used to support collection of VCS change when VcsRoot
properties were changed (e.g. password, login). VCS Plugin implementation is intended to
coves such cases. VCS Plugin should return no changes if fromRepository
and toRepository
are unrelated
fromRepository
is null
if it is the same as toRepository
fromRepository
and toRepository
has same VcsRoot.getVcsName()
fromRepository
and toRepository
are unrelatedfromState
should contain at least one statetoState
could be empty so VCS Plugin MUST compute CollectRepositoryChangesPolicy.getCurrentState(VcsRoot)
implicitlytoRepository
fromRepository
- repository from which to collect changes (if not the same as toRepository
)fromState
- start point for collecting changes in fromRepository (excluding)toRepository
- root to which changes should be collectedtoState
- end point for collecting changes in toRepositorycheckoutRules
- rulesconsumer
- callback to submit collected changes. Exceptions should be re-thrown.VcsException
- in the case of any errorsChangesConsumer