-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
False positive: OakConstraint0025: /apps/acs-commons[[nt:folder]]: Unexpected child node install found in a new node #92
Comments
Agreed. Nothing about that |
@kwin I'm not going to be able to run any builds myself until April 4 at the earliest (I'm between laptops until then). Do you know if there is a possibility that AutoSave can commit between adding a child node and setting its primary type when it is a folder that doesn't contain a .content.xml file? |
I don't think that the primary type is modified but is set to nt:folder during creation already by FileVault. |
Reproduced on java 11 with relevant oakpal execution log output:
|
constraint violation appears to be detected here: https://github.com/apache/jackrabbit-oak/blob/73d9ec9823723bf2fa7741e557614cb89dc6962b/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/nodetype/TypeEditor.java#L487 |
@kwin oakpal is currently linked to version 3.4.4 of filevault, and the relevant logic is happening in The order of extraction is:
The constraint violation on autosave is confusing, because it looks like But actually, the When the It is the next autosave after this point that fails with the constraint violation, because the The reason this isn't reproduced when installing the I think the proper resolution is to configure oakpal-maven-plugin in acs-aem-commons/pom.xml with an
I'll submit a PR with this change and any other related fixes and request a review from you. |
Thanks for the analysis. This behavior of FileVault was introduced with https://issues.apache.org/jira/browse/JCRVLT-417. Although some regressions were already fixed with https://issues.apache.org/jira/browse/JCRVLT-544 it seems we need another exclusion for nt:unstructured in FileVault to catch this edge case. |
In Adobe-Consulting-Services/acs-aem-commons@2d17ee5#diff-d8b13fb5ab2dc98ee98e3347a250f6517268c27b716832b47e3d76969f6a3654R151 I had to disable oakpal-maven-plugin:scan as otherwise the following build exception was emitted:
The actual installation in a repository works fine and both the
install
node as well as the parent/apps/acs-aem-commons
node are of typent:folder
which is perfectly valid.The text was updated successfully, but these errors were encountered: