Template Policy is not deploying with different naming convention

Avatar

Avatar

TUmesh

Avatar

TUmesh

TUmesh

20-04-2020

Hi Members,

In my current project template policies are named like policy_<some hash> but I have created one template policy with different naming convention like in below image with RED underlined, when I deploy the code with -PautoInstallPackage maven profile it does not deploy that policy with different naming convention.

So my question is that is there any place where I need to make this policy or naming convention enable to be picked up by Maven ?

 

Policy.png

Looking for your kindly response.

Thanks

Umesh Thakur

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Arun_Patidar

MVP

Total Posts

2.9K

Likes

958

Correct Answer

820

Avatar

Arun_Patidar

MVP

Total Posts

2.9K

Likes

958

Correct Answer

820
Arun_Patidar
MVP

20-04-2020

Hi,

There is no restriction in naming. Can you try to create manually?

I believe the issue is with filter.xml where you had filter mode merge, that mean no update from code to AEM. 

 

For policy try to add new filter without mode and then check.

https://jackrabbit.apache.org/filevault/filter.html

Answers (1)

Answers (1)

Avatar

Avatar

ArpitVarshney

MVP

Avatar

ArpitVarshney

MVP

ArpitVarshney
MVP

20-04-2020

Hi @TUmesh 

Can you verify filter.xml (which is present in the META-INF/vault directory) file of your aem codebase which defines what parts of the JCR repository are imported or exported during the respective operations through vlt or package management.

 

Regards,

Arpit