we have added workflow models in codebase under ui.content\src\main\content\jcr_root\conf\global\settings\workflow\models and ui.content\src\main\content\jcr_root\var\workflow\models. This was working fine. After downgrading file vault version from 1.3.6 to 1.1.4, getting below errors. Does anyone have a solution for this?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Thanks @anupampat for helping. Issue got resolved.
It is not about the filter root mapping. Filter root mapping are properly configured. Found a workaround for this issue to get fixed by disabling nodetype validation.
<jackrabbit-nodetypes>
<isDisabled>true</isDisabled>
</jackrabbit-nodetypes>
Adding this in ui.content/pom.xml file under <validatorsSettings> fixed the plugin issue and build also getting success.
Hi @TejaswiniS1 ,
Please check https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/filter-xml-validationviola... you will have to define them in your repository-structure .
Regards,
Anupam Patra
Hi @anupampat ,
Thanks for your response. But in our repository structure, we already having filter.xml file, where roots paths of workflows are configured.
Here it is
Views
Replies
Total Likes
@anupampat
Root paths are mentioned under validator settings. Below screenshot for reference of pom file.
But I realized, there is an error with plugin.
"Failed to execute mojo org.apache.jackrabbit:filevault-package-maven-plugin:1.1.4:validate-files {execution: default-validate-files} (org.apache.jackrabbit:filevault-package-maven-plugin:1.1.4:validate-files:default-validate-files:process-classes)"
Can you please let me know the solution if you have any?
Views
Replies
Total Likes
Hi @TejaswiniS1 ,
Is this the POM of repository structure ? You will need to add /conf as a root path in repository structure's POM if not already done. Like this - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/interesting-error-with-fil...
Thanks @anupampat for helping. Issue got resolved.
It is not about the filter root mapping. Filter root mapping are properly configured. Found a workaround for this issue to get fixed by disabling nodetype validation.
<jackrabbit-nodetypes>
<isDisabled>true</isDisabled>
</jackrabbit-nodetypes>
Adding this in ui.content/pom.xml file under <validatorsSettings> fixed the plugin issue and build also getting success.
Ref for the above solution: https://github.com/adobe/aem-guides-wknd/blob/main/ui.content/pom.xml