[jira] [Commented] (JCRVLT-120) Allow to filter content properties based on property name and value

2019-08-14 Thread Tobias Bocanegra (JIRA)


[ 
https://issues.apache.org/jira/browse/JCRVLT-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907459#comment-16907459
 ] 

Tobias Bocanegra commented on JCRVLT-120:
-

it's a). it should behave consistently. excluded properties are neither removed 
or updated, if they are not present in the package.

so the example:
{code}

  
  

{code}

it should not remove the {{cq:lastReplicated}} of existing content.
 

> Allow to filter content properties based on property name and value 
> 
>
> Key: JCRVLT-120
> URL: https://issues.apache.org/jira/browse/JCRVLT-120
> Project: Jackrabbit FileVault
>  Issue Type: Improvement
>  Components: vlt
>Affects Versions: 3.1.26
>Reporter: Timothee Maret
>Priority: Major
> Fix For: 3.1.28
>
> Attachments: JCRVLT-120.patch, JCRVLT-120.patch, JCRVLT-120.patch
>
>
> In our use case, we need to filter content distributed by filevault for 
> properties {{cq:lastReplicated}}, {{cq:lastReplicatedBy}} and 
> {{cq:lastReplicationAction}}.
> This feature could cover more than those three property and instead be 
> generalised to filter any property which name and value match the configured 
> filter. 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


Re: [VOTE] Release Apache Jackrabbit Oak 1.10.4

2019-08-14 Thread Marcel Reutegger
Hi,

On 12.08.19, 11:55, "Nitin Gupta"  wrote:
> Please vote on releasing this package as Apache Jackrabbit Oak 1.10.4.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.

All checks OK.

+1 Release this package as Apache Jackrabbit Oak 1.10.4

Regards
 Marcel



Re: New Jackrabbit Committer: Mohit Kataria

2019-08-14 Thread Woonsan Ko
Welcome, Mohit!

Cheers,

Woonsan

On Wed, Aug 14, 2019 at 2:31 AM Tommaso Teofili
 wrote:
>
> Welcome to the team Mohit!
>
> Regards,
> Tommaso
>
> On Thu, 8 Aug 2019 at 08:33, Marcel Reutegger  wrote:
>>
>> Hi,
>>
>> Please welcome Mohit Kataria as a new committer and PMC member of
>> the Apache Jackrabbit project. The Jackrabbit PMC recently decided to
>> offer Mohit committership based on his contributions. I'm happy to
>> announce that he accepted the offer and that all the related
>> administrative work has now been taken care of.
>>
>> Welcome to the team, Mohit!
>>
>> Regards
>>  Marcel
>>


Re: New Jackrabbit Committer: Nitin Gupta

2019-08-14 Thread Woonsan Ko
Welcome, Nitin!

Cheers,

Woonsan

On Wed, Aug 14, 2019 at 2:30 AM Tommaso Teofili
 wrote:
>
> Welcome to the team Nitin!
>
> Regards,
> Tommaso
>
> On Thu, 8 Aug 2019 at 08:31, Marcel Reutegger  wrote:
>>
>> Hi,
>>
>> Please welcome Nitin Gupta as a new committer and PMC member of
>> the Apache Jackrabbit project. The Jackrabbit PMC recently decided to
>> offer Nitin committership based on his contributions. I'm happy to
>> announce that he accepted the offer and that all the related
>> administrative work has now been taken care of.
>>
>> Welcome to the team, Nitin!
>>
>> Regards
>>  Marcel
>>


BUILD FAILURE: Jackrabbit Oak - Build # 2318 - Failure

2019-08-14 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit Oak (build #2318)

Status: Failure

Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/2318/ to 
view the results.

Changes:
[mreutegg] OAK-8538: Incomplete recovery on long running merge with branch 
commits

Add ignored tests

 

Test results:
1 tests failed.
FAILED:  
org.apache.jackrabbit.oak.plugins.index.lucene.directory.ConcurrentCopyOnReadDirectoryTest.concurrentPrefetchWithTimeout

Error Message:
null

Stack Trace:
java.lang.NullPointerException
at 
org.apache.jackrabbit.oak.plugins.index.lucene.directory.ConcurrentCopyOnReadDirectoryTest.concurrentPrefetchWithTimeout(ConcurrentCopyOnReadDirectoryTest.java:154)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)<>


Re: New Jackrabbit Committer: Mohit Kataria

2019-08-14 Thread Tommaso Teofili
Welcome to the team Mohit!

Regards,
Tommaso

On Thu, 8 Aug 2019 at 08:33, Marcel Reutegger  wrote:

> Hi,
>
> Please welcome Mohit Kataria as a new committer and PMC member of
> the Apache Jackrabbit project. The Jackrabbit PMC recently decided to
> offer Mohit committership based on his contributions. I'm happy to
> announce that he accepted the offer and that all the related
> administrative work has now been taken care of.
>
> Welcome to the team, Mohit!
>
> Regards
>  Marcel
>
>


Re: New Jackrabbit Committer: Nitin Gupta

2019-08-14 Thread Tommaso Teofili
Welcome to the team Nitin!

Regards,
Tommaso

On Thu, 8 Aug 2019 at 08:31, Marcel Reutegger  wrote:

> Hi,
>
> Please welcome Nitin Gupta as a new committer and PMC member of
> the Apache Jackrabbit project. The Jackrabbit PMC recently decided to
> offer Nitin committership based on his contributions. I'm happy to
> announce that he accepted the offer and that all the related
> administrative work has now been taken care of.
>
> Welcome to the team, Nitin!
>
> Regards
>  Marcel
>
>


Re: New Jackrabbit Committer: Nitin Gupta

2019-08-14 Thread Tommaso Teofili
Welcome to the team Nitin!

Regards,
Tommaso

On Thu, 8 Aug 2019 at 08:31, Marcel Reutegger  wrote:

> Hi,
>
> Please welcome Nitin Gupta as a new committer and PMC member of
> the Apache Jackrabbit project. The Jackrabbit PMC recently decided to
> offer Nitin committership based on his contributions. I'm happy to
> announce that he accepted the offer and that all the related
> administrative work has now been taken care of.
>
> Welcome to the team, Nitin!
>
> Regards
>  Marcel
>
>


Re: New Jackrabbit Committer: Mohit Kataria

2019-08-14 Thread Tommaso Teofili
Welcome to the team Mohit!

Regards,
Tommaso

On Thu, 8 Aug 2019 at 08:33, Marcel Reutegger  wrote:

> Hi,
>
> Please welcome Mohit Kataria as a new committer and PMC member of
> the Apache Jackrabbit project. The Jackrabbit PMC recently decided to
> offer Mohit committership based on his contributions. I'm happy to
> announce that he accepted the offer and that all the related
> administrative work has now been taken care of.
>
> Welcome to the team, Mohit!
>
> Regards
>  Marcel
>
>


[jira] [Commented] (JCRVLT-120) Allow to filter content properties based on property name and value

2019-08-14 Thread Konrad Windszus (JIRA)


[ 
https://issues.apache.org/jira/browse/JCRVLT-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906970#comment-16906970
 ] 

Konrad Windszus commented on JCRVLT-120:


I am currently preparing a patch for the documentation in 
https://jackrabbit.apache.org/filevault/filter.html for this feature. The 
desired behaviour for the import is not quite clear for me when property 
filtering is being used though. Should excluded properties below covered nodes 
of a package
a) not be touched in the repository
b) be removed

According to 
https://issues.apache.org/jira/browse/JCRVLT-120?focusedCommentId=15396063=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15396063
 it seems to be b) which is quite confusing because in fact excluded nodes 
(with no package filtering) are rather following the approach a).

Also the description says "based on property name and value" but I only see 
filtering being supported based on property name (not on the value).
[~tripod] or [~marett] Can you guys clarify?

> Allow to filter content properties based on property name and value 
> 
>
> Key: JCRVLT-120
> URL: https://issues.apache.org/jira/browse/JCRVLT-120
> Project: Jackrabbit FileVault
>  Issue Type: Improvement
>  Components: vlt
>Affects Versions: 3.1.26
>Reporter: Timothee Maret
>Priority: Major
> Fix For: 3.1.28
>
> Attachments: JCRVLT-120.patch, JCRVLT-120.patch, JCRVLT-120.patch
>
>
> In our use case, we need to filter content distributed by filevault for 
> properties {{cq:lastReplicated}}, {{cq:lastReplicatedBy}} and 
> {{cq:lastReplicationAction}}.
> This feature could cover more than those three property and instead be 
> generalised to filter any property which name and value match the configured 
> filter. 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)