Expand my Community achievements bar.

Join us in celebrating the outstanding achievement of our AEM Community Member of the Year!
SOLVED

Filter mode not working as expected in vault/content-package-maven-plugin

Avatar

Level 2

Hi all,

according to the doc, the content-package-maven-plugin has a new feature "mode" which sounds extremely helpful.

However, when I use it, it's not working as expected.

Does anybody have experience with this?

The META-INF/vault/filter.xml generated by the maven plugin looks ok:

<?xml version="1.0" encoding="UTF-8"?> <workspaceFilter version="1.0"> <filter root="/apps/dummy/dummyMerge" mode="merge"> <include pattern="/apps/dummy/dummyMerge(/.*)" /> </filter> <filter root="/apps/dummy/dummyReplace"> <include pattern="/apps/dummy/dummyReplace(/.*)" /> </filter> <filter root="/apps/dummy/dummyUpdate" mode="update"> <include pattern="/apps/dummy/dummyUpdate(/.*)" /> </filter> </workspaceFilter>

However, when installed, the following things are not the way I'd expect them:

- update and replace behave identically: when I delete a file or a property, mode "update" deltes this from the repo

- merge addes new files to the repo, but if I add a subnode or a property (e.g. in a dialog), this is not added to the repo

 

Has anyone used this successfully?

thanks,

Ben

 

btw: I'm using CQ5.6.1 with content-package-maven-plugin 0.0.20

1 Accepted Solution

Avatar

Correct answer by
Former Community Member
1 Reply

Avatar

Correct answer by
Former Community Member

I had the exact same problem, check the links on this forum post for answers!

 

http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----