[jira] [Commented] (OAK-8768) failed TokenCleanupTest.testExpiredReachingThreshold

2019-11-14 Thread Angela Schreiber (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16974482#comment-16974482
 ] 

Angela Schreiber commented on OAK-8768:
---

[~stefanegli], I ran the build with {{mvn -B verify -Prelease 
-Dtest.opts.memory=-Xmx2048m}} as indicated above but didn't manage to 
reproduce the failure. any idea how to get there?

> failed TokenCleanupTest.testExpiredReachingThreshold
> 
>
> Key: OAK-8768
> URL: https://issues.apache.org/jira/browse/OAK-8768
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.18.0
>Reporter: Stefan Egli
>Priority: Minor
>
> The following test failure was encountered in one of the {{oak-core}} test 
> runs (potential surefire details not available unfortunately) at rev 1869782:
> {noformat}mvn -B verify -Prelease -Dtest.opts.memory=-Xmx2048m
> [...]
> [INFO] Running 
> org.apache.jackrabbit.oak.security.authentication.token.TokenCleanupTest
> [ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.342 
> s <<< FAILURE! - in 
> org.apache.jackrabbit.oak.security.authentication.token.TokenCleanupTest
> [ERROR] 
> testExpiredReachingThreshold(org.apache.jackrabbit.oak.security.authentication.token.TokenCleanupTest)
>   Time elapsed: 0.182 s  <<< FAILURE!
> java.lang.AssertionError: expected:<50> but was:<54>
>   at 
> org.apache.jackrabbit.oak.security.authentication.token.TokenCleanupTest.assertTokenNodes(TokenCleanupTest.java:48)
>   at 
> org.apache.jackrabbit.oak.security.authentication.token.TokenCleanupTest.testExpiredReachingThreshold(TokenCleanupTest.java:83)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OAK-8766) Build Jackrabbit Oak #2499 failed

2019-11-14 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16974364#comment-16974364
 ] 

Hudson commented on OAK-8766:
-

Build is still failing.
Failed run: [Jackrabbit Oak 
#2500|https://builds.apache.org/job/Jackrabbit%20Oak/2500/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/2500/console]

> Build Jackrabbit Oak #2499 failed
> -
>
> Key: OAK-8766
> URL: https://issues.apache.org/jira/browse/OAK-8766
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #2499 has failed.
> First failed run: [Jackrabbit Oak 
> #2499|https://builds.apache.org/job/Jackrabbit%20Oak/2499/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/2499/console]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (OAK-7937) Implement CugAccessControlManager.getEffectivePolicies(Set principals)

2019-11-14 Thread Angela Schreiber (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-7937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Angela Schreiber resolved OAK-7937.
---
Resolution: Fixed

> Implement CugAccessControlManager.getEffectivePolicies(Set 
> principals)
> -
>
> Key: OAK-7937
> URL: https://issues.apache.org/jira/browse/OAK-7937
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: authorization-cug, security
>Reporter: Angela Schreiber
>Assignee: Angela Schreiber
>Priority: Major
> Fix For: 1.20.0
>
>
> today CugAccessControlManager.getEffectivePolicies(Set principals) 
> returns an empty array and has a comment stating that this is not implemented.
> having thought this through again, i think there was some benefit in having 
> the implementation. as long as the given set of principal does NOT include 
> everyone the return value should just include the CUG-policies that 
> explicitly list any of principals. IF _everyone_  was part of the set, the 
> return-value basically includes _all_ CUG-policies, because every CUG will 
> deny read-access for everyone except for the principals explicitly listed in 
> the CUG-policy... if we do the latter as lazy as possible it might still be 
> doable even in a scenario, when there are tons of CUG-policies specified.
> [~stillalex], wdyt? do you want to take care of this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OAK-7937) Implement CugAccessControlManager.getEffectivePolicies(Set principals)

2019-11-14 Thread Angela Schreiber (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-7937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16974259#comment-16974259
 ] 

Angela Schreiber commented on OAK-7937:
---

Applied patch with minor modifications and additional tests
Committed revision 1869794.


> Implement CugAccessControlManager.getEffectivePolicies(Set 
> principals)
> -
>
> Key: OAK-7937
> URL: https://issues.apache.org/jira/browse/OAK-7937
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: authorization-cug, security
>Reporter: Angela Schreiber
>Assignee: Angela Schreiber
>Priority: Major
> Fix For: 1.20.0
>
>
> today CugAccessControlManager.getEffectivePolicies(Set principals) 
> returns an empty array and has a comment stating that this is not implemented.
> having thought this through again, i think there was some benefit in having 
> the implementation. as long as the given set of principal does NOT include 
> everyone the return value should just include the CUG-policies that 
> explicitly list any of principals. IF _everyone_  was part of the set, the 
> return-value basically includes _all_ CUG-policies, because every CUG will 
> deny read-access for everyone except for the principals explicitly listed in 
> the CUG-policy... if we do the latter as lazy as possible it might still be 
> doable even in a scenario, when there are tons of CUG-policies specified.
> [~stillalex], wdyt? do you want to take care of this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (OAK-8767) CugAccessControlManager.getEffectivePolicies(String) throws PathNotFoundException if parent node is not accessible

2019-11-14 Thread Angela Schreiber (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Angela Schreiber resolved OAK-8767.
---
Resolution: Fixed

Committed revision 1869794.


> CugAccessControlManager.getEffectivePolicies(String) throws 
> PathNotFoundException if parent node is not accessible
> --
>
> Key: OAK-8767
> URL: https://issues.apache.org/jira/browse/OAK-8767
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: authorization-cug
>Reporter: Angela Schreiber
>Assignee: Angela Schreiber
>Priority: Major
> Fix For: 1.20.0
>
>
> while working on OAK-7937 i noticed that 
> {{CugAccessControlManager.getEffectivePolicies(String absPath)}} will fail 
> with {{PathNotFoundException}} if any of the ancestor nodes is not 
> accessible. Instead it should only verify that the target node exists. In 
> contrast non-accessible ancestors will just be excluded from the evaluation 
> of effective policies as it is the case when the attached ac-content is not 
> readable.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OAK-8625) oak-upgrade leaks empty test folders

2019-11-14 Thread Julian Reschke (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-8625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-8625:

Labels:   (was: candidate_oak_1_8)

> oak-upgrade leaks empty test folders
> 
>
> Key: OAK-8625
> URL: https://issues.apache.org/jira/browse/OAK-8625
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: upgrade
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.18.0, 1.10.6
>
> Attachments: OAK-8625.diff
>
>
> This is because of using {{com.google.common.io.Files#createTempDir()}} 
> without cleanup up afterwards.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (OAK-8624) oak-run: tests leak mapd temp files

2019-11-14 Thread Julian Reschke (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16931524#comment-16931524
 ] 

Julian Reschke edited comment on OAK-8624 at 11/14/19 12:49 PM:


trunk: (1.18.0) [r1867061|http://svn.apache.org/r1867061]
1.10: (1.10.6) [r1867841|http://svn.apache.org/r1867841]
1.8: [r1869792|http://svn.apache.org/r1869792]



was (Author: reschke):
trunk: (1.18.0) [r1867061|http://svn.apache.org/r1867061]
1.10: [r1867841|http://svn.apache.org/r1867841]


> oak-run: tests leak mapd temp files
> ---
>
> Key: OAK-8624
> URL: https://issues.apache.org/jira/browse/OAK-8624
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_6
> Fix For: 1.18.0, 1.8.18, 1.10.6
>
> Attachments: OAK-8624.diff
>
>
> This is because {{MapDBMapFactory}} is backed by temporary DB, but that one 
> is never closed.
> Fix:
> - make it {{closeable}}
> - adapt test case and use in {{RecoveryCommand}}
> However, {{RecoveryCommand}} sets the {{MapFactory}} instance globally, and 
> never resets it. Thus, if the factory is indeed closed, subsequent tests will 
> fail. So, in {{RecoveryCommand}}, restore the default factory when done.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OAK-8624) oak-run: tests leak mapd temp files

2019-11-14 Thread Julian Reschke (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-8624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-8624:

Fix Version/s: 1.8.18

> oak-run: tests leak mapd temp files
> ---
>
> Key: OAK-8624
> URL: https://issues.apache.org/jira/browse/OAK-8624
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.18.0, 1.8.18, 1.10.6
>
> Attachments: OAK-8624.diff
>
>
> This is because {{MapDBMapFactory}} is backed by temporary DB, but that one 
> is never closed.
> Fix:
> - make it {{closeable}}
> - adapt test case and use in {{RecoveryCommand}}
> However, {{RecoveryCommand}} sets the {{MapFactory}} instance globally, and 
> never resets it. Thus, if the factory is indeed closed, subsequent tests will 
> fail. So, in {{RecoveryCommand}}, restore the default factory when done.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OAK-8624) oak-run: tests leak mapd temp files

2019-11-14 Thread Julian Reschke (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-8624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-8624:

Labels: candidate_oak_1_6  (was: )

> oak-run: tests leak mapd temp files
> ---
>
> Key: OAK-8624
> URL: https://issues.apache.org/jira/browse/OAK-8624
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_6
> Fix For: 1.18.0, 1.8.18, 1.10.6
>
> Attachments: OAK-8624.diff
>
>
> This is because {{MapDBMapFactory}} is backed by temporary DB, but that one 
> is never closed.
> Fix:
> - make it {{closeable}}
> - adapt test case and use in {{RecoveryCommand}}
> However, {{RecoveryCommand}} sets the {{MapFactory}} instance globally, and 
> never resets it. Thus, if the factory is indeed closed, subsequent tests will 
> fail. So, in {{RecoveryCommand}}, restore the default factory when done.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OAK-8624) oak-run: tests leak mapd temp files

2019-11-14 Thread Julian Reschke (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-8624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-8624:

Labels:   (was: candidate_oak_1_8)

> oak-run: tests leak mapd temp files
> ---
>
> Key: OAK-8624
> URL: https://issues.apache.org/jira/browse/OAK-8624
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 1.18.0, 1.8.18, 1.10.6
>
> Attachments: OAK-8624.diff
>
>
> This is because {{MapDBMapFactory}} is backed by temporary DB, but that one 
> is never closed.
> Fix:
> - make it {{closeable}}
> - adapt test case and use in {{RecoveryCommand}}
> However, {{RecoveryCommand}} sets the {{MapFactory}} instance globally, and 
> never resets it. Thus, if the factory is indeed closed, subsequent tests will 
> fail. So, in {{RecoveryCommand}}, restore the default factory when done.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (OAK-8768) failed TokenCleanupTest.testExpiredReachingThreshold

2019-11-14 Thread Stefan Egli (Jira)
Stefan Egli created OAK-8768:


 Summary: failed TokenCleanupTest.testExpiredReachingThreshold
 Key: OAK-8768
 URL: https://issues.apache.org/jira/browse/OAK-8768
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: core
Affects Versions: 1.18.0
Reporter: Stefan Egli


The following test failure was encountered in one of the {{oak-core}} test runs 
(potential surefire details not available unfortunately) at rev 1869782:
{noformat}mvn -B verify -Prelease -Dtest.opts.memory=-Xmx2048m

[...]

[INFO] Running 
org.apache.jackrabbit.oak.security.authentication.token.TokenCleanupTest
[ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.342 s 
<<< FAILURE! - in 
org.apache.jackrabbit.oak.security.authentication.token.TokenCleanupTest
[ERROR] 
testExpiredReachingThreshold(org.apache.jackrabbit.oak.security.authentication.token.TokenCleanupTest)
  Time elapsed: 0.182 s  <<< FAILURE!
java.lang.AssertionError: expected:<50> but was:<54>
at 
org.apache.jackrabbit.oak.security.authentication.token.TokenCleanupTest.assertTokenNodes(TokenCleanupTest.java:48)
at 
org.apache.jackrabbit.oak.security.authentication.token.TokenCleanupTest.testExpiredReachingThreshold(TokenCleanupTest.java:83)
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OAK-8710) AbstractLoginModule#logout() must not remove 'foreign' principals/credentials

2019-11-14 Thread Angela Schreiber (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-8710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Angela Schreiber updated OAK-8710:
--
Fix Version/s: (was: 1.20.0)

> AbstractLoginModule#logout() must not remove 'foreign' principals/credentials 
> --
>
> Key: OAK-8710
> URL: https://issues.apache.org/jira/browse/OAK-8710
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: auth-external, core, security-spi
>Reporter: Manfred Baedke
>Assignee: Angela Schreiber
>Priority: Major
> Attachments: OAK-8710.patch, logout.png
>
>
> See 
> https://github.com/apache/jackrabbit-oak/blob/9569d659f0655d3ba16c1cfe1fbb5f53959f701f/oak-security-spi/src/main/java/org/apache/jackrabbit/oak/spi/security/authentication/AbstractLoginModule.java#L189:
> The criterion for logout() to succeed is
> {code}!subject.getPrincipals().isEmpty() && 
> !subject.getPublicCredentials(Credentials.class).isEmpty(){code}
> This did not work in a case where the subject was created by a thread 
> handling an authenticated JMX connection (and later passed on to other 
> threads due to AccessControlContext inheritage).
> I'd propose to make logout() succeed unconditionally, but I'm not entirely 
> sure about side effects.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OAK-7937) Implement CugAccessControlManager.getEffectivePolicies(Set principals)

2019-11-14 Thread Angela Schreiber (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-7937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Angela Schreiber updated OAK-7937:
--
Fix Version/s: 1.20.0

> Implement CugAccessControlManager.getEffectivePolicies(Set 
> principals)
> -
>
> Key: OAK-7937
> URL: https://issues.apache.org/jira/browse/OAK-7937
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: authorization-cug, security
>Reporter: Angela Schreiber
>Assignee: Angela Schreiber
>Priority: Major
> Fix For: 1.20.0
>
>
> today CugAccessControlManager.getEffectivePolicies(Set principals) 
> returns an empty array and has a comment stating that this is not implemented.
> having thought this through again, i think there was some benefit in having 
> the implementation. as long as the given set of principal does NOT include 
> everyone the return value should just include the CUG-policies that 
> explicitly list any of principals. IF _everyone_  was part of the set, the 
> return-value basically includes _all_ CUG-policies, because every CUG will 
> deny read-access for everyone except for the principals explicitly listed in 
> the CUG-policy... if we do the latter as lazy as possible it might still be 
> doable even in a scenario, when there are tons of CUG-policies specified.
> [~stillalex], wdyt? do you want to take care of this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OAK-8767) CugAccessControlManager.getEffectivePolicies(String) throws PathNotFoundException if parent node is not accessible

2019-11-14 Thread Angela Schreiber (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Angela Schreiber updated OAK-8767:
--
Fix Version/s: 1.20.0

> CugAccessControlManager.getEffectivePolicies(String) throws 
> PathNotFoundException if parent node is not accessible
> --
>
> Key: OAK-8767
> URL: https://issues.apache.org/jira/browse/OAK-8767
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: authorization-cug
>Reporter: Angela Schreiber
>Assignee: Angela Schreiber
>Priority: Major
> Fix For: 1.20.0
>
>
> while working on OAK-7939 i noticed that 
> {{CugAccessControlManager.getEffectivePolicies(String absPath)}} will fail 
> with {{PathNotFoundException}} if any of the ancestor nodes is not 
> accessible. Instead it should only verify that the target node exists. In 
> contrast non-accessible ancestors will just be excluded from the evaluation 
> of effective policies as it is the case when the attached ac-content is not 
> readable.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (OAK-8767) CugAccessControlManager.getEffectivePolicies(String) throws PathNotFoundException if parent node is not accessible

2019-11-14 Thread Angela Schreiber (Jira)
Angela Schreiber created OAK-8767:
-

 Summary: CugAccessControlManager.getEffectivePolicies(String) 
throws PathNotFoundException if parent node is not accessible
 Key: OAK-8767
 URL: https://issues.apache.org/jira/browse/OAK-8767
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: authorization-cug
Reporter: Angela Schreiber
Assignee: Angela Schreiber


while working on OAK-7939 i noticed that 
{{CugAccessControlManager.getEffectivePolicies(String absPath)}} will fail with 
{{PathNotFoundException}} if any of the ancestor nodes is not accessible. 
Instead it should only verify that the target node exists. In contrast 
non-accessible ancestors will just be excluded from the evaluation of effective 
policies as it is the case when the attached ac-content is not readable.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OAK-8767) CugAccessControlManager.getEffectivePolicies(String) throws PathNotFoundException if parent node is not accessible

2019-11-14 Thread Angela Schreiber (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Angela Schreiber updated OAK-8767:
--
Description: while working on OAK-7937 i noticed that 
{{CugAccessControlManager.getEffectivePolicies(String absPath)}} will fail with 
{{PathNotFoundException}} if any of the ancestor nodes is not accessible. 
Instead it should only verify that the target node exists. In contrast 
non-accessible ancestors will just be excluded from the evaluation of effective 
policies as it is the case when the attached ac-content is not readable.  (was: 
while working on OAK-7939 i noticed that 
{{CugAccessControlManager.getEffectivePolicies(String absPath)}} will fail with 
{{PathNotFoundException}} if any of the ancestor nodes is not accessible. 
Instead it should only verify that the target node exists. In contrast 
non-accessible ancestors will just be excluded from the evaluation of effective 
policies as it is the case when the attached ac-content is not readable.)

> CugAccessControlManager.getEffectivePolicies(String) throws 
> PathNotFoundException if parent node is not accessible
> --
>
> Key: OAK-8767
> URL: https://issues.apache.org/jira/browse/OAK-8767
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: authorization-cug
>Reporter: Angela Schreiber
>Assignee: Angela Schreiber
>Priority: Major
> Fix For: 1.20.0
>
>
> while working on OAK-7937 i noticed that 
> {{CugAccessControlManager.getEffectivePolicies(String absPath)}} will fail 
> with {{PathNotFoundException}} if any of the ancestor nodes is not 
> accessible. Instead it should only verify that the target node exists. In 
> contrast non-accessible ancestors will just be excluded from the evaluation 
> of effective policies as it is the case when the attached ac-content is not 
> readable.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (OAK-8583) getNodeByIdentifier may fail with RuntimeException

2019-11-14 Thread Julian Reschke (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917805#comment-16917805
 ] 

Julian Reschke edited comment on OAK-8583 at 11/14/19 10:38 AM:


trunk: (1.18.0) [r1866041|http://svn.apache.org/r1866041] 
[r1866039|http://svn.apache.org/r1866039]
1.10: (1.10.6) [r1867824|http://svn.apache.org/r1867824]
1.8: [r1869789|http://svn.apache.org/r1869789]



was (Author: reschke):
trunk: (1.18.0) [r1866041|http://svn.apache.org/r1866041] 
[r1866039|http://svn.apache.org/r1866039]
1.10: [r1867824|http://svn.apache.org/r1867824]


> getNodeByIdentifier may fail with RuntimeException
> --
>
> Key: OAK-8583
> URL: https://issues.apache.org/jira/browse/OAK-8583
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: jcr
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_6
> Fix For: 1.18.0, 1.8.18, 1.10.6
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OAK-8583) getNodeByIdentifier may fail with RuntimeException

2019-11-14 Thread Julian Reschke (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-8583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-8583:

Fix Version/s: 1.8.18

> getNodeByIdentifier may fail with RuntimeException
> --
>
> Key: OAK-8583
> URL: https://issues.apache.org/jira/browse/OAK-8583
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: jcr
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.18.0, 1.8.18, 1.10.6
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OAK-8583) getNodeByIdentifier may fail with RuntimeException

2019-11-14 Thread Julian Reschke (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-8583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-8583:

Labels: candidate_oak_1_6  (was: candidate_oak_1_8)

> getNodeByIdentifier may fail with RuntimeException
> --
>
> Key: OAK-8583
> URL: https://issues.apache.org/jira/browse/OAK-8583
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: jcr
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_6
> Fix For: 1.18.0, 1.8.18, 1.10.6
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (OAK-8614) Update httpclient/mime dependencies to 4.5.10

2019-11-14 Thread Julian Reschke (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926478#comment-16926478
 ] 

Julian Reschke edited comment on OAK-8614 at 11/14/19 9:26 AM:
---

trunk: (1.18.0) [r1866734|http://svn.apache.org/r1866734]
1.10: (1.10.6) [r1867834|http://svn.apache.org/r1867834]
1.8: [r1869786|http://svn.apache.org/r1869786]



was (Author: reschke):
trunk: (1.18.0) [r1866734|http://svn.apache.org/r1866734]
1.10: [r1867834|http://svn.apache.org/r1867834]


> Update httpclient/mime dependencies to 4.5.10
> -
>
> Key: OAK-8614
> URL: https://issues.apache.org/jira/browse/OAK-8614
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_6
> Fix For: 1.18.0, 1.8.18, 1.10.6
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OAK-8614) Update httpclient/mime dependencies to 4.5.10

2019-11-14 Thread Julian Reschke (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-8614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-8614:

Labels: candidate_oak_1_6  (was: candidate_oak_1_8)

> Update httpclient/mime dependencies to 4.5.10
> -
>
> Key: OAK-8614
> URL: https://issues.apache.org/jira/browse/OAK-8614
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_6
> Fix For: 1.18.0, 1.8.18, 1.10.6
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OAK-8614) Update httpclient/mime dependencies to 4.5.10

2019-11-14 Thread Julian Reschke (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-8614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-8614:

Fix Version/s: 1.8.18

> Update httpclient/mime dependencies to 4.5.10
> -
>
> Key: OAK-8614
> URL: https://issues.apache.org/jira/browse/OAK-8614
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.18.0, 1.8.18, 1.10.6
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OAK-8760) ClusterViewDocument uses static instance og SimpleDateFormat

2019-11-14 Thread Stefan Egli (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16974076#comment-16974076
 ] 

Stefan Egli commented on OAK-8760:
--

bq. I was just going through SpotBugs warnings. I realize that this might be 
contentious, but my preference is to resolve these warnings even if not 
strictly needed to avoid future confusion.
+1 to fixing such warnings

> ClusterViewDocument uses static instance og SimpleDateFormat
> 
>
> Key: OAK-8760
> URL: https://issues.apache.org/jira/browse/OAK-8760
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: documentmk
>Reporter: Julian Reschke
>Priority: Minor
> Attachments: OAK-8760.diff
>
>
> ...which is not thread-safe.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (OAK-8766) Build Jackrabbit Oak #2499 failed

2019-11-14 Thread Hudson (Jira)
Hudson created OAK-8766:
---

 Summary: Build Jackrabbit Oak #2499 failed
 Key: OAK-8766
 URL: https://issues.apache.org/jira/browse/OAK-8766
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: continuous integration
Reporter: Hudson


No description is provided

The build Jackrabbit Oak #2499 has failed.
First failed run: [Jackrabbit Oak 
#2499|https://builds.apache.org/job/Jackrabbit%20Oak/2499/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/2499/console]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OAK-8598) Update httpcore dependency to 4.4.12

2019-11-14 Thread Julian Reschke (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-8598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-8598:

Labels: candidate_oak_1_6  (was: candidate_oak_1_8)

> Update httpcore dependency to 4.4.12
> 
>
> Key: OAK-8598
> URL: https://issues.apache.org/jira/browse/OAK-8598
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_6
> Fix For: 1.18.0, 1.8.18, 1.10.6
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (OAK-8598) Update httpcore dependency to 4.4.12

2019-11-14 Thread Julian Reschke (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923375#comment-16923375
 ] 

Julian Reschke edited comment on OAK-8598 at 11/14/19 8:26 AM:
---

trunk: (1.18.0) [r1866453|http://svn.apache.org/r1866453]
1.10: (1.10.6) [r1867825|http://svn.apache.org/r1867825]
1.8: [r1869782|http://svn.apache.org/r1869782]



was (Author: reschke):
trunk: (1.18.0) [r1866453|http://svn.apache.org/r1866453]
1.10: [r1867825|http://svn.apache.org/r1867825]


> Update httpcore dependency to 4.4.12
> 
>
> Key: OAK-8598
> URL: https://issues.apache.org/jira/browse/OAK-8598
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.18.0, 1.8.18, 1.10.6
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OAK-8598) Update httpcore dependency to 4.4.12

2019-11-14 Thread Julian Reschke (Jira)


 [ 
https://issues.apache.org/jira/browse/OAK-8598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-8598:

Fix Version/s: 1.8.18

> Update httpcore dependency to 4.4.12
> 
>
> Key: OAK-8598
> URL: https://issues.apache.org/jira/browse/OAK-8598
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
>  Labels: candidate_oak_1_8
> Fix For: 1.18.0, 1.8.18, 1.10.6
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)