Hello Angela, > On 16 Mar 2016, at 12:39, Angela Schreiber <[email protected]> wrote: > > stepping into the AbstractOak2OakTest and finally > RepositorySidegrade.copyState i actually see that the target NodeBuilder > that results from copyWorkspace doesn't have the jcr:mixinTypes > property copied from the src to the target, which consequently
Indeed, it seems there’s a bug, which causes the RepositorySidegrade to skip the root node properties. I think the reason lies in the calculateEffectiveIncludePaths() method, which produces an effective list of paths to migrate. If we have a ‘/‘ in the input list, the method will replace it with a list of ‘/‘ children and the root itself is removed from the list. Similar issue is present in the RepositoryUpgrade, but it isn’t so dangerous there, as we create the root node anyway using an initializer. Created OAK-4128 to track this. However, the OAK-4128 is reproducible and present not only on the JDBC destination, so I guess the random failures (including the ones on Jenkins) are related to something else. Best regards, Tomek -- Tomek Rękawek | Adobe Research | www.adobe.com [email protected]
