We are working on multiple projects, which all root from the same sub-node and somehow the two different projects have diverged on a root node to the project.
- Project 1 path: /content/subnode/project1
- Project 2 path: /content/subnode/project2
My problem is with subnode
Project 1 Installed first: subnode type is nt:folder (it actually doesn't have .content.xml in the source code)
Project 2 installed second: subnode type is sling:orderedFolder Building locally works fine. Building through our build system to test environment fails to install the package and throws nodeType Constraint exception do to subnode.
Now that the node is in the system as nt:folder I have a mental check to make sure all our projects under this node (6-7 projects). If any projects in a new environment get installed in a different order and happen to have a different node structure it breaks the build.
Is there a safer node type that won't throw this exception and can just be overwritten for each project? Should I just make sure they are all nt:folder or sling:orderedFolder? My main objective here is to not have that node breaking an install.
Thanks