netcentric / aem-nodetypes Goto Github PK

<version>6.5.7.0</version>

[WARNING] ValidationViolation: "jackrabbit-nodetypes: {http://www.day.com/dam/1.0}cfVariationNode Skip validation of nodes with that type/name", filePath=jcr_root/content/dam/content-fragments/b2c/test-content/.../.content.xml, nodePath=/content/dam/content-fragments/b2c/test-content/.../jcr:content/data/master, line=25, column=66

This dam:cfVariationNode is automatically created when creating a Content Fragments.
<jcr:root xmlns:dam="http://www.day.com/dam/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0"
...
<master
jcr:mixinTypes="[cq:Taggable,dam:cfVariationNode]"
jcr:primaryType="nt:unstructured"

Would it be possible to add that node type or is it an AEM lib missing that type?
<aem.sdk.api>2022.10.9145.20221006T013555Z-220800</aem.sdk.api>

filevault package validation outputs a warning like this

[WARNING] ValidationViolation: "jackrabbit-nodetypes: crx: is not a registered namespace prefix. Skip validation of nodes with that type/name", filePath=jcr_root\conf\filevaultsample\settings\wcm\policies\_rep_policy.xml, nodePath=/conf/filevaultsample/settings/wcm/policies/rep:policy/allow1, line=11, column=49

if the package contains an ACL definition with a rule like this:

    <allow1
        jcr:primaryType="rep:GrantACE"
        rep:principalName="content-authors"
        rep:privileges="{Name}[crx:replicate,jcr:read]"/>

the crx namespace is missing from the cnd files here.

a lot of other namespaces are missing as well (e.g. all those that are often used in DAM metadata like Iptc4xmpCore. by what process was the list of namespaces defined? manually or in some automatic process?

Hello.

When adding a MSM blueprint definition in the project, the maven build returns this error:
[ERROR] ValidationViolation: "jackrabbit-nodetypes: Node 'dialog [cq:Dialog]' is not allowed as child of node with types [nt:folder]: Node type does not allow arbitrary child nodes and does not allow this specific name and node type either!", filePath=jcr_root\apps\msm\myapp-blueprint\_jcr_content\dialog.xml, nodePath=/apps/msm/myapp-blueprint/jcr:content/dialog, line=4, column=23

Steps to reproduce:

1. Create a project from AEM project archetype (tested with version 39)
2. Create a Blueprint definition from AEM Admin UI (http://localhost:4502/libs/wcm/msm/gui/content/blueprintconfig.html). Named it 'myapp-blueprint', for this example.
3. Add the path to the ui.apps filter.xml file, in your project (filter root="/apps/msm/myapp-blueprint")
4. Import the blueprint definition structure, from the repository to your project (I used Visual Studio, 'Import from AEM Server' option). You'll find the new files in your project under ui.apps\src\main\content\jcr_root\apps\msm\myapp-blueprint.
5. Execute the build (mvn clean install -PautoInstallPackage)

Recent AEMaaCS versions added a new mixin and potentially contain other updates. A new CND from the most recent AEM 2023.10.xx should be provided.