// in case of group member changes, the "cascade" is sync, hence
// we have no ordering problem as we have with async updates of proxy/hosted
// reposes on boot
prefixFileUpdateListener.reset();
final MavenGroupRepository mgr =
getRepositoryRegistry().getRepositoryWithFacet(GROUP1_REPO_ID, MavenGroupRepository.class);
mgr.removeMemberRepositoryId(HOSTED1_REPO_ID);
getApplicationConfiguration().saveConfiguration();
waitForRoutingBackgroundUpdates();
assertThat(prefixFileUpdateListener.getPublished(), contains(GROUP1_REPO_ID, GROUP2_REPO_ID));
mgr.addMemberRepositoryId(HOSTED1_REPO_ID);
getApplicationConfiguration().saveConfiguration();
waitForRoutingBackgroundUpdates();
assertThat(prefixFileUpdateListener.getPublished(),
contains(GROUP1_REPO_ID, GROUP2_REPO_ID, GROUP1_REPO_ID, GROUP2_REPO_ID));