[
https://issues.apache.org/jira/browse/JCRVLT-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342518#comment-17342518
]
Iago Amorín Fernández commented on JCRVLT-519:
----------------------------------------------
Thanks for your answer, [~kwin] .
In fact, these are the dependencies in my project:
{code:java}
<dependencies>
<dependency>
<groupId>org.apache.jackrabbit</groupId>
<artifactId>filevault-package-maven-plugin</artifactId>
<version>1.1.6</version>
</dependency>
<dependency>
<groupId>org.apache.jackrabbit.vault</groupId>
<artifactId>org.apache.jackrabbit.vault</artifactId>
<version>3.4.10</version>
</dependency>
</dependencies>
{code}
... where the second one was added simply for reinforcing what you suggested
about the vault's version, even if the filevault's version includes the proper
dependency:
[https://mvnrepository.com/artifact/org.apache.jackrabbit/filevault-package-maven-plugin/1.1.6]
!Captura de pantalla 2021-05-11 a las 14.18.51.png!
So I think this isn't a dependency problem.
> Filter with explicit include/exclude definitions still overwrites existing
> properties
> -------------------------------------------------------------------------------------
>
> Key: JCRVLT-519
> URL: https://issues.apache.org/jira/browse/JCRVLT-519
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Affects Versions: 3.4.0
> Reporter: Iago Amorín Fernández
> Priority: Major
> Fix For: 3.4.12
>
> Attachments: .content.xml, Captura de pantalla 2021-05-10 a las
> 13.43.09.png, Captura de pantalla 2021-05-11 a las 14.18.51.png, filter.xml,
> testConfiguration.zip
>
>
> I need to update just a given set of properties within a configuration node,
> leacing both children nodes and previously existing properties unchanged.
> So, when having a previously existing configuration as the one present in
> [^testConfiguration.zip] if we try to load the file
> *jcr_root/conf/test/_sling_configs/TestConfiguration/.content.xml*
> [^.content.xml] with a content like this:
> {code:java}
> <?xml version="1.0" encoding="UTF-8"?>
> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0";
> xmlns:cq="http://www.day.com/jcr/cq/1.0";
> xmlns:jcr="http://www.jcp.org/jcr/1.0";
> xmlns:mix="http://www.jcp.org/jcr/mix/1.0";
> xmlns:nt="http://www.jcp.org/jcr/nt/1.0";
> jcr:primaryType="cq:Page">
> <jcr:content
> jcr:primaryType="cq:PageContent"
> property1="1.changed">
> </jcr:content>
> </jcr:root>
> {code}
> ... using this filter definition like this [^filter.xml] :
> {code:java}
> <?xml version="1.0" encoding="UTF-8"?>
> <workspaceFilter version="1.0">
> <filter root="/conf/test" mode="update">
> <exclude
> pattern="/conf/test/sling:configs/TestConfiguration/jcr:content(/.*)?"
> matchProperties="true"/>
> <include
> pattern="/conf/test/sling:configs/TestConfiguration/jcr:content/property1"
> matchProperties="true"/>
> </filter>
> </workspaceFilter>
> {code}
> ... we have an undesired result: It's keeping the child nodes intact but the
> {{jcr:content}} is being completely overridden:
> !Captura de pantalla 2021-05-10 a las 13.43.09.png| thumbnail!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
