Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

How to fix No enum constant org.apache.jackrabbit.vault.fs.api.ImportMode.UPDATE_PROPERTIES .error ?

Avatar

Community Advisor

Hi all

 

   As per https://jackrabbit.apache.org/filevault/filter.html update  filter is deprecated and we need to use update_properties instead. But this doesn't work . When we replacfe this filter, the build fails with an error which says No enum constant org.apache.jackrabbit.vault.fs.api.ImportMode.UPDATE_PROPERTIES .  Does any one know how we can solve this issue ?

 

Thanks

Veena

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @kautuk_sahni Oh . actually forgot to update here. I did update the pom.xml to get the latest bundles as I mentioned in https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-fix-no-enum-constan... . But that resulted in a loop of issues. Since it need time and effort to change and resolve all the issues and then make sure the project is not affected, we decided not to make that change and hence we went ahead with "update" mode itself. That meant , any chnage we made via code for /conf wont get deployed and we are now manually packaging it from our local and installing it as a separate package. 

View solution in original post

9 Replies

Avatar

Community Advisor

Hi @VeenaVikraman 
Could you please check the fileVault bundle (Apache Jackrabbit FileVault Core Bundle(org.apache.jackrabbit.vault) ) version in AEM , for me its 3.4.0 and the link you have shared it is for Version: 3.7.2 

 

I think update_properties is introduced in 3.6.4

https://issues.apache.org/jira/browse/JCRVLT-643 

https://github.com/apache/jackrabbit-filevault/commit/383356c109e0d2a1b4e3478ec389d80937e6292b 



Arun Patidar

Avatar

Community Advisor

Thanks @arunpatidar 

I am not sure if I am looking at the right values, but this is what I see in my pom.xml. I cannot find org.apache.jackrabbit.vault specifically. 

 

VeenaVikraman_0-1706006088164.png

 

Avatar

Community Advisor

I think , I got this . I updated this version to the latest one , which inturn downloaded the org.apache.jackrabbit.vault latest version of 3.7.2 . But changing this is spiraling into many more issues in the validations. 

 

VeenaVikraman_0-1706007681607.png

 

Avatar

Community Advisor

Please check this with your AEM version as well, otherwise package installation won't be working as expected if AEM has bundle lower than 3.6.4



Arun Patidar

Avatar

Community Advisor

That's strange. I don't see the vault package deployed in my Felix console at all .... I am using AEM as Cloud 

VeenaVikraman_0-1706009979870.png

 

Avatar

Community Advisor

Hi @VeenaVikraman 
You need to check the bundles not the dependency .



Arun Patidar

Avatar

Community Advisor

Hi @VeenaVikraman 
you can search same AEM from system console

arunpatidar_0-1706008598601.png

 



Arun Patidar

Avatar

Administrator

@VeenaVikraman Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.



Kautuk Sahni

Avatar

Correct answer by
Community Advisor

Hi @kautuk_sahni Oh . actually forgot to update here. I did update the pom.xml to get the latest bundles as I mentioned in https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-fix-no-enum-constan... . But that resulted in a loop of issues. Since it need time and effort to change and resolve all the issues and then make sure the project is not affected, we decided not to make that change and hence we went ahead with "update" mode itself. That meant , any chnage we made via code for /conf wont get deployed and we are now manually packaging it from our local and installing it as a separate package.