[jira] [Commented] (OAK-1588) Create more tests/validation to LDAP integration
[
https://issues.apache.org/jira/browse/OAK-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256611#comment-16256611
]
Alex Deparvu commented on OAK-1588:
---
I reduced the min coverage to 0.85 to get the builds running again
(http://svn.apache.org/viewvc?rev=1815553=rev).
> Create more tests/validation to LDAP integration
>
>
> Key: OAK-1588
> URL: https://issues.apache.org/jira/browse/OAK-1588
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: auth-ldap
>Reporter: angela
> Labels: test
> Fix For: 1.8, 1.7.12
>
>
> this is a follow up issue for the remaining tasks as mentioned by [~tripod]
> in OAK-516:
> {quote}
> [...] needs more testing, validation [...]
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (OAK-6962) Build Jackrabbit Oak #986 failed
[ https://issues.apache.org/jira/browse/OAK-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Deparvu closed OAK-6962. - > Build Jackrabbit Oak #986 failed > > > Key: OAK-6962 > URL: https://issues.apache.org/jira/browse/OAK-6962 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #986 has failed. > First failed run: [Jackrabbit Oak > #986|https://builds.apache.org/job/Jackrabbit%20Oak/986/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/986/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6962) Build Jackrabbit Oak #986 failed
[ https://issues.apache.org/jira/browse/OAK-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Deparvu resolved OAK-6962. --- Resolution: Duplicate > Build Jackrabbit Oak #986 failed > > > Key: OAK-6962 > URL: https://issues.apache.org/jira/browse/OAK-6962 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #986 has failed. > First failed run: [Jackrabbit Oak > #986|https://builds.apache.org/job/Jackrabbit%20Oak/986/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/986/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6962) Build Jackrabbit Oak #986 failed
[ https://issues.apache.org/jira/browse/OAK-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255897#comment-16255897 ] Hudson commented on OAK-6962: - Build is still failing. Failed run: [Jackrabbit Oak #987|https://builds.apache.org/job/Jackrabbit%20Oak/987/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/987/console] > Build Jackrabbit Oak #986 failed > > > Key: OAK-6962 > URL: https://issues.apache.org/jira/browse/OAK-6962 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #986 has failed. > First failed run: [Jackrabbit Oak > #986|https://builds.apache.org/job/Jackrabbit%20Oak/986/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/986/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-1588) Create more tests/validation to LDAP integration
[
https://issues.apache.org/jira/browse/OAK-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255789#comment-16255789
]
Alex Deparvu commented on OAK-1588:
---
there was one failure of the CI machine related to the coverage (OAK-6962),
which I don't see locally:
bq. [WARNING] Rule violated for bundle oak-auth-ldap: lines covered ratio is
0.85, but expected minimum is 0.86
> Create more tests/validation to LDAP integration
>
>
> Key: OAK-1588
> URL: https://issues.apache.org/jira/browse/OAK-1588
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: auth-ldap
>Reporter: angela
> Labels: test
> Fix For: 1.8, 1.7.12
>
>
> this is a follow up issue for the remaining tasks as mentioned by [~tripod]
> in OAK-516:
> {quote}
> [...] needs more testing, validation [...]
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6962) Build Jackrabbit Oak #986 failed
Hudson created OAK-6962: --- Summary: Build Jackrabbit Oak #986 failed Key: OAK-6962 URL: https://issues.apache.org/jira/browse/OAK-6962 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit Oak #986 has failed. First failed run: [Jackrabbit Oak #986|https://builds.apache.org/job/Jackrabbit%20Oak/986/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/986/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6408) Review package exports for o.a.j.oak.plugins.index.*
[ https://issues.apache.org/jira/browse/OAK-6408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-6408: Fix Version/s: 1.8 > Review package exports for o.a.j.oak.plugins.index.* > > > Key: OAK-6408 > URL: https://issues.apache.org/jira/browse/OAK-6408 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core, indexing >Reporter: angela > Fix For: 1.8 > > > while working on OAK-6304 and OAK-6355, i noticed that the > _o.a.j.oak.plugins.index.*_ contains both internal api/utilities and > implementation details which get equally exported (though without having any > package export version set). > in the light of the modularization effort, i would like to suggest that we > try to sort that out and separate the _public_ parts from implementation > details. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6961) Remove package export for org.apache.jackrabbit.oak.plugins.index.property.jmx
[ https://issues.apache.org/jira/browse/OAK-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-6961: Attachment: OAK-6961.patch > Remove package export for org.apache.jackrabbit.oak.plugins.index.property.jmx > -- > > Key: OAK-6961 > URL: https://issues.apache.org/jira/browse/OAK-6961 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core, parent, query >Reporter: angela >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > Attachments: OAK-6961.patch > > > [~tmueller], following OAK-6826 I think we are able to remove the package > export for _org.apache.jackrabbit.oak.plugins.index.property.jmx_ which is no > longer used in non-test code outside of oak-core. At the same time the entry > in the baseline filter in the parent/pom.xml should be removed. > cc: [~stillalex] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6960) Remove package export for org.apache.jackrabbit.oak.plugins.index.nodetype
[ https://issues.apache.org/jira/browse/OAK-6960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-6960: Summary: Remove package export for org.apache.jackrabbit.oak.plugins.index.nodetype (was: CLONE - Remove package export for org.apache.jackrabbit.oak.plugins.index.nodetype) > Remove package export for org.apache.jackrabbit.oak.plugins.index.nodetype > -- > > Key: OAK-6960 > URL: https://issues.apache.org/jira/browse/OAK-6960 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core, parent, query >Reporter: angela >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > Attachments: OAK-6960.patch > > > [~tmueller], following OAK-6826 I think we are able to remove the package > export for _org.apache.jackrabbit.oak.plugins.index.nodetype_ which is no > longer used in non-test code outside of oak-core. At the same time the entry > in the baseline filter in the parent/pom.xml should be removed. > cc: [~stillalex] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6961) CLONE - CLONE - Remove package export for org.apache.jackrabbit.oak.plugins.index.property.jmx
[ https://issues.apache.org/jira/browse/OAK-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-6961: Description: [~tmueller], following OAK-6826 I think we are able to remove the package export for _org.apache.jackrabbit.oak.plugins.index.property.jmx_ which is no longer used in non-test code outside of oak-core. At the same time the entry in the baseline filter in the parent/pom.xml should be removed. cc: [~stillalex] was: [~tmueller], following OAK-6826 I think we are able to remove the package export for _org.apache.jackrabbit.oak.plugins.index.nodetype_ which is no longer used in non-test code outside of oak-core. At the same time the entry in the baseline filter in the parent/pom.xml should be removed. cc: [~stillalex] > CLONE - CLONE - Remove package export for > org.apache.jackrabbit.oak.plugins.index.property.jmx > -- > > Key: OAK-6961 > URL: https://issues.apache.org/jira/browse/OAK-6961 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core, parent, query >Reporter: angela >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > > [~tmueller], following OAK-6826 I think we are able to remove the package > export for _org.apache.jackrabbit.oak.plugins.index.property.jmx_ which is no > longer used in non-test code outside of oak-core. At the same time the entry > in the baseline filter in the parent/pom.xml should be removed. > cc: [~stillalex] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6961) Remove package export for org.apache.jackrabbit.oak.plugins.index.property.jmx
[ https://issues.apache.org/jira/browse/OAK-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-6961: Summary: Remove package export for org.apache.jackrabbit.oak.plugins.index.property.jmx (was: CLONE - CLONE - Remove package export for org.apache.jackrabbit.oak.plugins.index.property.jmx) > Remove package export for org.apache.jackrabbit.oak.plugins.index.property.jmx > -- > > Key: OAK-6961 > URL: https://issues.apache.org/jira/browse/OAK-6961 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core, parent, query >Reporter: angela >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > > [~tmueller], following OAK-6826 I think we are able to remove the package > export for _org.apache.jackrabbit.oak.plugins.index.property.jmx_ which is no > longer used in non-test code outside of oak-core. At the same time the entry > in the baseline filter in the parent/pom.xml should be removed. > cc: [~stillalex] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6961) CLONE - CLONE - Remove package export for org.apache.jackrabbit.oak.plugins.index.property.jmx
angela created OAK-6961: --- Summary: CLONE - CLONE - Remove package export for org.apache.jackrabbit.oak.plugins.index.property.jmx Key: OAK-6961 URL: https://issues.apache.org/jira/browse/OAK-6961 Project: Jackrabbit Oak Issue Type: Technical task Components: core, parent, query Reporter: angela Assignee: Thomas Mueller Fix For: 1.8, 1.7.12 [~tmueller], following OAK-6826 I think we are able to remove the package export for _org.apache.jackrabbit.oak.plugins.index.nodetype_ which is no longer used in non-test code outside of oak-core. At the same time the entry in the baseline filter in the parent/pom.xml should be removed. cc: [~stillalex] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6960) CLONE - Remove package export for org.apache.jackrabbit.oak.plugins.index.nodetype
[ https://issues.apache.org/jira/browse/OAK-6960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-6960: Attachment: OAK-6960.patch [~tmueller] proposed patch attached. > CLONE - Remove package export for > org.apache.jackrabbit.oak.plugins.index.nodetype > -- > > Key: OAK-6960 > URL: https://issues.apache.org/jira/browse/OAK-6960 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core, parent, query >Reporter: angela >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > Attachments: OAK-6960.patch > > > [~tmueller], following OAK-6826 I think we are able to remove the package > export for _org.apache.jackrabbit.oak.plugins.index.nodetype_ which is no > longer used in non-test code outside of oak-core. At the same time the entry > in the baseline filter in the parent/pom.xml should be removed. > cc: [~stillalex] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6960) CLONE - Remove package export for org.apache.jackrabbit.oak.plugins.index.nodetype
[ https://issues.apache.org/jira/browse/OAK-6960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-6960: Description: [~tmueller], following OAK-6826 I think we are able to remove the package export for _org.apache.jackrabbit.oak.plugins.index.nodetype_ which is no longer used in non-test code outside of oak-core. At the same time the entry in the baseline filter in the parent/pom.xml should be removed. cc: [~stillalex] was: [~tmueller], following OAK-6826 I think we are able to remove the package export for _org.apache.jackrabbit.oak.plugins.index.counter_ which is no longer used in non-test code outside of oak-core. At the same time the entry in the baseline filter in the parent/pom.xml should be removed. cc: [~stillalex] > CLONE - Remove package export for > org.apache.jackrabbit.oak.plugins.index.nodetype > -- > > Key: OAK-6960 > URL: https://issues.apache.org/jira/browse/OAK-6960 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core, parent, query >Reporter: angela >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > > [~tmueller], following OAK-6826 I think we are able to remove the package > export for _org.apache.jackrabbit.oak.plugins.index.nodetype_ which is no > longer used in non-test code outside of oak-core. At the same time the entry > in the baseline filter in the parent/pom.xml should be removed. > cc: [~stillalex] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6960) CLONE - Remove package export for org.apache.jackrabbit.oak.plugins.index.nodetype
angela created OAK-6960: --- Summary: CLONE - Remove package export for org.apache.jackrabbit.oak.plugins.index.nodetype Key: OAK-6960 URL: https://issues.apache.org/jira/browse/OAK-6960 Project: Jackrabbit Oak Issue Type: Technical task Components: core, parent, query Reporter: angela Assignee: Thomas Mueller Fix For: 1.8, 1.7.12 [~tmueller], following OAK-6826 I think we are able to remove the package export for _org.apache.jackrabbit.oak.plugins.index.counter_ which is no longer used in non-test code outside of oak-core. At the same time the entry in the baseline filter in the parent/pom.xml should be removed. cc: [~stillalex] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6959) Remove package export for org.apache.jackrabbit.oak.plugins.index.counter
[ https://issues.apache.org/jira/browse/OAK-6959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-6959: Fix Version/s: 1.7.12 > Remove package export for org.apache.jackrabbit.oak.plugins.index.counter > - > > Key: OAK-6959 > URL: https://issues.apache.org/jira/browse/OAK-6959 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core, parent, query >Reporter: angela >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > Attachments: OAK-6959.patch > > > [~tmueller], following OAK-6826 I think we are able to remove the package > export for _org.apache.jackrabbit.oak.plugins.index.counter_ which is no > longer used in non-test code outside of oak-core. At the same time the entry > in the baseline filter in the parent/pom.xml should be removed. > cc: [~stillalex] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6959) Remove package export for org.apache.jackrabbit.oak.plugins.index.counter
[ https://issues.apache.org/jira/browse/OAK-6959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-6959: Attachment: OAK-6959.patch [~tmueller], proposed patch attached. > Remove package export for org.apache.jackrabbit.oak.plugins.index.counter > - > > Key: OAK-6959 > URL: https://issues.apache.org/jira/browse/OAK-6959 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core, parent, query >Reporter: angela >Assignee: Thomas Mueller > Fix For: 1.8 > > Attachments: OAK-6959.patch > > > [~tmueller], following OAK-6826 I think we are able to remove the package > export for _org.apache.jackrabbit.oak.plugins.index.counter_ which is no > longer used in non-test code outside of oak-core. At the same time the entry > in the baseline filter in the parent/pom.xml should be removed. > cc: [~stillalex] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6959) Remove package export for org.apache.jackrabbit.oak.plugins.index.counter
angela created OAK-6959: --- Summary: Remove package export for org.apache.jackrabbit.oak.plugins.index.counter Key: OAK-6959 URL: https://issues.apache.org/jira/browse/OAK-6959 Project: Jackrabbit Oak Issue Type: Technical task Components: core, parent, query Reporter: angela Assignee: Thomas Mueller [~tmueller], following OAK-6826 I think we are able to remove the package export for _org.apache.jackrabbit.oak.plugins.index.counter_ which is no longer used in non-test code outside of oak-core. At the same time the entry in the baseline filter in the parent/pom.xml should be removed. cc: [~stillalex] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6958) Remove package export for org.apache.jackrabbit.oak.plugins.atomic
[ https://issues.apache.org/jira/browse/OAK-6958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela resolved OAK-6958. - Resolution: Fixed Fix Version/s: 1.7.12 Committed revision 1815495. > Remove package export for org.apache.jackrabbit.oak.plugins.atomic > -- > > Key: OAK-6958 > URL: https://issues.apache.org/jira/browse/OAK-6958 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core >Reporter: angela > Fix For: 1.8, 1.7.12 > > > Following OAK-6826 I think we are able to remove the package export for > _org.apache.jackrabbit.oak.plugins.atomic_ which is no longer used in > non-test code outside of _oak-core_. At the same time the entry in the > baseline filter in the parent/pom.xml should be removed. > [~mduerig], [~stillalex], [~mreutegg], I will run the build with the proposed > changes including ITs and would go ahead removing the export if it succeeds. > Feel free to revert if you oppose the change for some reason I cannot see > from looking at the code or if I missed something. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6958) Remove package export for org.apache.jackrabbit.oak.plugins.atomic
[ https://issues.apache.org/jira/browse/OAK-6958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated OAK-6958: Description: Following OAK-6826 I think we are able to remove the package export for _org.apache.jackrabbit.oak.plugins.atomic_ which is no longer used in non-test code outside of _oak-core_. At the same time the entry in the baseline filter in the parent/pom.xml should be removed. [~mduerig], [~stillalex], [~mreutegg], I will run the build with the proposed changes including ITs and would go ahead removing the export if it succeeds. Feel free to revert if you oppose the change for some reason I cannot see from looking at the code or if I missed something. was: Following OAK-6826 I think we are able to remove the package export for _org.apache.jackrabbit.oak.plugins.atomic_ which is no longer used in non-test code outside of _oak-core_. At the same time the entry in the baseline filter in the parent/pom.xml should be removed. [~mduerig], [~stillalex], [~mreutegg], I will run the build with the proposed changes including ITs and would go ahead removing the export if it succeeds. Feel free to revert if you oppose the change for some reason I cannot see from looking at the code. > Remove package export for org.apache.jackrabbit.oak.plugins.atomic > -- > > Key: OAK-6958 > URL: https://issues.apache.org/jira/browse/OAK-6958 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core >Reporter: angela > Fix For: 1.8, 1.7.12 > > > Following OAK-6826 I think we are able to remove the package export for > _org.apache.jackrabbit.oak.plugins.atomic_ which is no longer used in > non-test code outside of _oak-core_. At the same time the entry in the > baseline filter in the parent/pom.xml should be removed. > [~mduerig], [~stillalex], [~mreutegg], I will run the build with the proposed > changes including ITs and would go ahead removing the export if it succeeds. > Feel free to revert if you oppose the change for some reason I cannot see > from looking at the code or if I missed something. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6958) Remove package export for org.apache.jackrabbit.oak.plugins.atomic
angela created OAK-6958: --- Summary: Remove package export for org.apache.jackrabbit.oak.plugins.atomic Key: OAK-6958 URL: https://issues.apache.org/jira/browse/OAK-6958 Project: Jackrabbit Oak Issue Type: Technical task Components: core Reporter: angela Following OAK-6826 I think we are able to remove the package export for _org.apache.jackrabbit.oak.plugins.atomic_ which is no longer used in non-test code outside of _oak-core_. At the same time the entry in the baseline filter in the parent/pom.xml should be removed. [~mduerig], [~stillalex], [~mreutegg], I will run the build with the proposed changes including ITs and would go ahead removing the export if it succeeds. Feel free to revert if you oppose the change for some reason I cannot see from looking at the code. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6954) Build Jackrabbit Oak #982 failed
[ https://issues.apache.org/jira/browse/OAK-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255679#comment-16255679 ] Hudson commented on OAK-6954: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #985|https://builds.apache.org/job/Jackrabbit%20Oak/985/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/985/console] > Build Jackrabbit Oak #982 failed > > > Key: OAK-6954 > URL: https://issues.apache.org/jira/browse/OAK-6954 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #982 has failed. > First failed run: [Jackrabbit Oak > #982|https://builds.apache.org/job/Jackrabbit%20Oak/982/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/982/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6957) Remove export for org.apache.jackrabbit.oak.security
[
https://issues.apache.org/jira/browse/OAK-6957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255669#comment-16255669
]
Alex Deparvu commented on OAK-6957:
---
Isn't this (almost) the same as removing the SecurityProviderImpl class from an
OSGi point of view (or moving it with the tests)? If we only deprecate the
class now, it makes sense to keep this export until we remove it (or move it to
test).
> Remove export for org.apache.jackrabbit.oak.security
>
>
> Key: OAK-6957
> URL: https://issues.apache.org/jira/browse/OAK-6957
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, security
>Reporter: angela
> Fix For: 1.8
>
>
> [~stillalex], with the fix you provided for the {{Jcr}} class we should be
> able drop the export for _org.apache.jackrabbit.oak.security_
> Looking for remaining usages I noticed OAK-6956, which I will link to this
> issue.
> Apart from that, what's your take on this?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6221) Deprecate SecurityProviderImpl
[
https://issues.apache.org/jira/browse/OAK-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255664#comment-16255664
]
Alex Deparvu commented on OAK-6221:
---
yeah, I wanted to get this in before 1.8. I'll pick up the patch again with
fresh eyes, if it seems doable I'll set the fix version to reflect it.
> Deprecate SecurityProviderImpl
> --
>
> Key: OAK-6221
> URL: https://issues.apache.org/jira/browse/OAK-6221
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, security
>Reporter: Alex Deparvu
>Assignee: Alex Deparvu
>
> As agreed on OAK-6172, the {{SecurityProviderImpl}} should be deprecated in
> favor of the {{InternalSecurityProvider}}.
> This should also cover coming up with a way to use the new version in tests
> while we figure out OSGi testing setups.
> fyi [~anchela]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OAK-6955) Remove export for org.apache.jackrabbit.oak.plugins.itemsave
[ https://issues.apache.org/jira/browse/OAK-6955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela resolved OAK-6955. - Resolution: Fixed Fix Version/s: 1.7.12 Committed revision 1815491. > Remove export for org.apache.jackrabbit.oak.plugins.itemsave > > > Key: OAK-6955 > URL: https://issues.apache.org/jira/browse/OAK-6955 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core >Reporter: angela > Fix For: 1.8, 1.7.12 > > > With the fix in OAK-6826 the package > _org.apache.jackrabbit.oak.plugins.itemsave_ is no longer used outside of > _oak-core_ and I would suggest we remove the export (and the filter entry in > the parent/pom.xml). > [~stillalex], [~mduerig], [~mreutegg] unless you object, I will run the build > with ITs and commit the fix if that passes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6957) Remove export for org.apache.jackrabbit.oak.security
angela created OAK-6957:
---
Summary: Remove export for org.apache.jackrabbit.oak.security
Key: OAK-6957
URL: https://issues.apache.org/jira/browse/OAK-6957
Project: Jackrabbit Oak
Issue Type: Technical task
Components: core, security
Reporter: angela
[~stillalex], with the fix you provided for the {{Jcr}} class we should be able
drop the export for _org.apache.jackrabbit.oak.security_
Looking for remaining usages I noticed OAK-6956, which I will link to this
issue.
Apart from that, what's your take on this?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6956) RepositoryUpgrade hardcodes SecurityProvider
[
https://issues.apache.org/jira/browse/OAK-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-6956:
Fix Version/s: 1.8
> RepositoryUpgrade hardcodes SecurityProvider
>
>
> Key: OAK-6956
> URL: https://issues.apache.org/jira/browse/OAK-6956
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: upgrade
>Reporter: angela
> Fix For: 1.8
>
>
> [~tomek.rekawek] Looking at non-test usage of the (to be deprecated)
> {{SecurityProviderImpl}} I noticed one usage in the {{RepositoryUpgrade}}
> that looks troublesome to me.
> I would strongly recommend to fix that given the fact that we no longer use
> {{SecurityProviderImpl}} in production ready setup scenarios.
> cc: [~stillalex]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6956) RepositoryUpgrade hardcodes SecurityProvider
[
https://issues.apache.org/jira/browse/OAK-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-6956:
Priority: Critical (was: Major)
> RepositoryUpgrade hardcodes SecurityProvider
>
>
> Key: OAK-6956
> URL: https://issues.apache.org/jira/browse/OAK-6956
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: upgrade
>Reporter: angela
>Priority: Critical
> Fix For: 1.8
>
>
> [~tomek.rekawek] Looking at non-test usage of the (to be deprecated)
> {{SecurityProviderImpl}} I noticed one usage in the {{RepositoryUpgrade}}
> that looks troublesome to me.
> I would strongly recommend to fix that given the fact that we no longer use
> {{SecurityProviderImpl}} in production ready setup scenarios.
> cc: [~stillalex]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6956) RepositoryUpgrade hardcodes SecurityProvider
angela created OAK-6956:
---
Summary: RepositoryUpgrade hardcodes SecurityProvider
Key: OAK-6956
URL: https://issues.apache.org/jira/browse/OAK-6956
Project: Jackrabbit Oak
Issue Type: Bug
Components: upgrade
Reporter: angela
[~tomek.rekawek] Looking at non-test usage of the (to be deprecated)
{{SecurityProviderImpl}} I noticed one usage in the {{RepositoryUpgrade}} that
looks troublesome to me.
I would strongly recommend to fix that given the fact that we no longer use
{{SecurityProviderImpl}} in production ready setup scenarios.
cc: [~stillalex]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6955) Remove export for org.apache.jackrabbit.oak.plugins.itemsave
angela created OAK-6955: --- Summary: Remove export for org.apache.jackrabbit.oak.plugins.itemsave Key: OAK-6955 URL: https://issues.apache.org/jira/browse/OAK-6955 Project: Jackrabbit Oak Issue Type: Technical task Reporter: angela With the fix in OAK-6826 the package _org.apache.jackrabbit.oak.plugins.itemsave_ is no longer used outside of _oak-core_ and I would suggest we remove the export (and the filter entry in the parent/pom.xml). [~stillalex], [~mduerig], [~mreutegg] unless you object, I will run the build with ITs and commit the fix if that passes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-1588) Create more tests/validation to LDAP integration
[
https://issues.apache.org/jira/browse/OAK-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved OAK-1588.
-
Resolution: Fixed
Fix Version/s: (was: 1.10)
1.7.12
1.8
Committed revision 1815479.
[~stillalex], fyi
> Create more tests/validation to LDAP integration
>
>
> Key: OAK-1588
> URL: https://issues.apache.org/jira/browse/OAK-1588
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: auth-ldap
>Reporter: angela
> Labels: test
> Fix For: 1.8, 1.7.12
>
>
> this is a follow up issue for the remaining tasks as mentioned by [~tripod]
> in OAK-516:
> {quote}
> [...] needs more testing, validation [...]
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6954) Build Jackrabbit Oak #982 failed
[ https://issues.apache.org/jira/browse/OAK-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255548#comment-16255548 ] Hudson commented on OAK-6954: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #984|https://builds.apache.org/job/Jackrabbit%20Oak/984/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/984/console] > Build Jackrabbit Oak #982 failed > > > Key: OAK-6954 > URL: https://issues.apache.org/jira/browse/OAK-6954 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #982 has failed. > First failed run: [Jackrabbit Oak > #982|https://builds.apache.org/job/Jackrabbit%20Oak/982/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/982/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-4887) Query cost estimation: ordering by an unindexed property not reflected
[ https://issues.apache.org/jira/browse/OAK-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255479#comment-16255479 ] Alexander Klimetschek commented on OAK-4887: Thanks! So I assume something else changed since 1.4.x. > Query cost estimation: ordering by an unindexed property not reflected > -- > > Key: OAK-4887 > URL: https://issues.apache.org/jira/browse/OAK-4887 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Affects Versions: 1.4.2 >Reporter: Alexander Klimetschek >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > > A query that orders by an unindexed property seems to have no effect on the > cost estimation, compared to the same query without the order by, although it > has a big impact on the execution performance for larger results/indexes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6951) Add package export versions for oak-query-spi
[ https://issues.apache.org/jira/browse/OAK-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved OAK-6951. - Resolution: Fixed > Add package export versions for oak-query-spi > - > > Key: OAK-6951 > URL: https://issues.apache.org/jira/browse/OAK-6951 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core >Reporter: angela >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > Attachments: OAK-6951.patch > > > [~tmueller], as discussed on monday the public query SPI should come with > explicit version management. > I will provide a proposed patch. > cc: [~mreutegg] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6951) Add package export versions for oak-query-spi
[ https://issues.apache.org/jira/browse/OAK-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255476#comment-16255476 ] Thomas Mueller commented on OAK-6951: - http://svn.apache.org/r1815471 (trunk) > Add package export versions for oak-query-spi > - > > Key: OAK-6951 > URL: https://issues.apache.org/jira/browse/OAK-6951 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core >Reporter: angela >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > Attachments: OAK-6951.patch > > > [~tmueller], as discussed on monday the public query SPI should come with > explicit version management. > I will provide a proposed patch. > cc: [~mreutegg] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6756) Convert oak-auth-external to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255463#comment-16255463 ] angela commented on OAK-6756: - [~ch...@die-schneider.net], cool... thanks a lot. I will take a look asap. > Convert oak-auth-external to OSGi R6 annotations > > > Key: OAK-6756 > URL: https://issues.apache.org/jira/browse/OAK-6756 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: auth-external >Reporter: Robert Munteanu >Assignee: angela > Fix For: 1.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6954) Build Jackrabbit Oak #982 failed
[ https://issues.apache.org/jira/browse/OAK-6954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255461#comment-16255461 ] Hudson commented on OAK-6954: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #983|https://builds.apache.org/job/Jackrabbit%20Oak/983/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/983/console] > Build Jackrabbit Oak #982 failed > > > Key: OAK-6954 > URL: https://issues.apache.org/jira/browse/OAK-6954 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #982 has failed. > First failed run: [Jackrabbit Oak > #982|https://builds.apache.org/job/Jackrabbit%20Oak/982/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/982/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6953) CacheLIRS cannot be disabled
[ https://issues.apache.org/jira/browse/OAK-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-6953: -- Labels: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4 candidate_oak_1_6 (was: ) > CacheLIRS cannot be disabled > > > Key: OAK-6953 > URL: https://issues.apache.org/jira/browse/OAK-6953 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, > candidate_oak_1_6 > Fix For: 1.8, 1.7.12 > > > The CacheLIRS cannot be disabled by setting the maxWeight to zero whereas the > Guava implementation can be disabled this way. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6953) CacheLIRS cannot be disabled
[ https://issues.apache.org/jira/browse/OAK-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-6953. --- Resolution: Fixed Fix Version/s: 1.7.12 Fixed in trunk: http://svn.apache.org/r1815466 > CacheLIRS cannot be disabled > > > Key: OAK-6953 > URL: https://issues.apache.org/jira/browse/OAK-6953 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, > candidate_oak_1_6 > Fix For: 1.8, 1.7.12 > > > The CacheLIRS cannot be disabled by setting the maxWeight to zero whereas the > Guava implementation can be disabled this way. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-2906) test failures for oak-auth-ldap on Windows
[ https://issues.apache.org/jira/browse/OAK-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-2906. - Resolution: Duplicate Fix Version/s: (was: 1.8) Fixed by fixing OAK-5358. > test failures for oak-auth-ldap on Windows > -- > > Key: OAK-2906 > URL: https://issues.apache.org/jira/browse/OAK-2906 > Project: Jackrabbit Oak > Issue Type: Bug > Components: auth-ldap >Affects Versions: 1.5.13 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: test > > testAuthenticateValidateTrueFalse(org.apache.jackrabbit.oak.security.authentication.ldap.LdapProviderTest) > Time elapsed: 0.01 sec <<< ERROR! > java.io.IOException: Unable to delete file: > target\apacheds\cache\5c3940f5-2ddb-4d47-8254-8b2266c1a684\ou=system.data > at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2279) > at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1653) > at > org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1535) > at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2270) > at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1653) > at > org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1535) > at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2270) > at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1653) > at > org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1535) > at > org.apache.jackrabbit.oak.security.authentication.ldap.AbstractServer.doDelete(AbstractServer.java:264) > at > org.apache.jackrabbit.oak.security.authentication.ldap.AbstractServer.setUp(AbstractServer.java:183) > at > org.apache.jackrabbit.oak.security.authentication.ldap.InternalLdapServer.setUp(InternalLdapServer.java:33) > etc... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-5358) test failures for oak-auth-ldap on Windows
[ https://issues.apache.org/jira/browse/OAK-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-5358: Labels: (was: candidate_oak_1_0) > test failures for oak-auth-ldap on Windows > -- > > Key: OAK-5358 > URL: https://issues.apache.org/jira/browse/OAK-5358 > Project: Jackrabbit Oak > Issue Type: Bug > Components: auth-ldap >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.0.36, 1.2.23, 1.4.12, 1.5.17, 1.6.0 > > > testAuthenticateValidateTrueFalse(org.apache.jackrabbit.oak.security.authentication.ldap.LdapProviderTest) > Time elapsed: 0.01 sec <<< ERROR! > java.io.IOException: Unable to delete file: > target\apacheds\cache\5c3940f5-2ddb-4d47-8254-8b2266c1a684\ou=system.data > at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2279) > at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1653) > at > org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1535) > at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2270) > at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1653) > at > org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1535) > at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2270) > at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1653) > at > org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1535) > at > org.apache.jackrabbit.oak.security.authentication.ldap.AbstractServer.doDelete(AbstractServer.java:264) > at > org.apache.jackrabbit.oak.security.authentication.ldap.AbstractServer.setUp(AbstractServer.java:183) > at > org.apache.jackrabbit.oak.security.authentication.ldap.InternalLdapServer.setUp(InternalLdapServer.java:33) > etc... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-2904) test failures for oak-auth-ldap on Windows
[ https://issues.apache.org/jira/browse/OAK-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255425#comment-16255425 ] Julian Reschke commented on OAK-2904: - trunk: [r1682088|http://svn.apache.org/r1682088] 1.2: [r1682125|http://svn.apache.org/r1682125] 1.0: [r1682124|http://svn.apache.org/r1682124] > test failures for oak-auth-ldap on Windows > -- > > Key: OAK-2904 > URL: https://issues.apache.org/jira/browse/OAK-2904 > Project: Jackrabbit Oak > Issue Type: Bug > Components: auth-ldap >Reporter: Julian Reschke > Fix For: 1.0.15, 1.2.3, 1.4 > > > testAuthenticateValidateTrueFalse(org.apache.jackrabbit.oak.security.authentication.ldap.LdapProviderTest) > Time elapsed: 0.01 sec <<< ERROR! > java.io.IOException: Unable to delete file: > target\apacheds\cache\5c3940f5-2ddb-4d47-8254-8b2266c1a684\ou=system.data > at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2279) > at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1653) > at > org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1535) > at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2270) > at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1653) > at > org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1535) > at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2270) > at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1653) > at > org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1535) > at > org.apache.jackrabbit.oak.security.authentication.ldap.AbstractServer.doDelete(AbstractServer.java:264) > at > org.apache.jackrabbit.oak.security.authentication.ldap.AbstractServer.setUp(AbstractServer.java:183) > at > org.apache.jackrabbit.oak.security.authentication.ldap.InternalLdapServer.setUp(InternalLdapServer.java:33) > etc... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-5455) Specify versions for maven plugins used in build for ensuring stable builds
[
https://issues.apache.org/jira/browse/OAK-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255415#comment-16255415
]
Julian Reschke commented on OAK-5455:
-
With these changes the only remaining instance of "The following plugins do not
have their version specified:" is in oak-examples/standalone:
{noformat}
[WARNING] The following plugins do not have their version specified:
[WARNING] maven-surefire-plugin (from super-pom) 2.20.1
{noformat}
But the parent pom *does* specify the version - so it seems the diagnostics are
incorrect.
> Specify versions for maven plugins used in build for ensuring stable builds
> ---
>
> Key: OAK-5455
> URL: https://issues.apache.org/jira/browse/OAK-5455
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: parent
>Reporter: Chetan Mehrotra
>Assignee: Julian Reschke
> Fix For: 1.8, 1.7.13
>
> Attachments: OAK-5455-v1.patch, enforce.diff
>
>
> Running a check for plugin versions used in oak build
> {noformat}
> mvn versions:display-plugin-updates
> {noformat}
> leads to following warning
> {noformat}
> [INFO] The following plugin updates are available:
> [INFO] org.apache.felix:maven-scr-plugin .. 1.16.0 -> 1.21.0
> [INFO]
> [WARNING] The following plugins do not have their version specified:
> [WARNING] maven-compiler-plugin .. 2.0.2
> [WARNING] maven-deploy-plugin . (from super-pom) 2.4
> [WARNING] maven-failsafe-plugin . 2.12.4
> [WARNING] maven-jar-plugin . 2.1
> [WARNING] maven-javadoc-plugin . 2.0
> [WARNING] maven-release-plugin . (from super-pom) 2.0-beta-4
> [WARNING] maven-resources-plugin ... 2.2
> [WARNING] maven-surefire-plugin .. 2.4.2
> [INFO]
> [WARNING] Project does not define minimum Maven version, default is: 2.0
> [INFO] Plugins require minimum Maven version of: 3.0.5
> [INFO] Note: the super-pom from Maven 3.3.9 defines some of the plugin
> [INFO] versions and may be influencing the plugins required minimum
> Maven
> [INFO] version.
> [INFO]
> [ERROR] Project does not define required minimum version of Maven.
> [ERROR] Update the pom.xml to contain
> [ERROR]
> [ERROR] 3.0.5
> [ERROR]
> {noformat}
> As a fix we should
> # Specify version for all maven plugin in use
> # Specify minimum version of maven to be used (version used in CI is 3.2.1)
> # Configure enforcer plugin to ensure that in future no plugin is used
> without specifying the version [1]
> [1] http://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OAK-5455) Specify versions for maven plugins used in build for ensuring stable builds
[
https://issues.apache.org/jira/browse/OAK-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved OAK-5455.
-
Resolution: Fixed
> Specify versions for maven plugins used in build for ensuring stable builds
> ---
>
> Key: OAK-5455
> URL: https://issues.apache.org/jira/browse/OAK-5455
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: parent
>Reporter: Chetan Mehrotra
>Assignee: Julian Reschke
> Fix For: 1.8, 1.7.13
>
> Attachments: OAK-5455-v1.patch, enforce.diff
>
>
> Running a check for plugin versions used in oak build
> {noformat}
> mvn versions:display-plugin-updates
> {noformat}
> leads to following warning
> {noformat}
> [INFO] The following plugin updates are available:
> [INFO] org.apache.felix:maven-scr-plugin .. 1.16.0 -> 1.21.0
> [INFO]
> [WARNING] The following plugins do not have their version specified:
> [WARNING] maven-compiler-plugin .. 2.0.2
> [WARNING] maven-deploy-plugin . (from super-pom) 2.4
> [WARNING] maven-failsafe-plugin . 2.12.4
> [WARNING] maven-jar-plugin . 2.1
> [WARNING] maven-javadoc-plugin . 2.0
> [WARNING] maven-release-plugin . (from super-pom) 2.0-beta-4
> [WARNING] maven-resources-plugin ... 2.2
> [WARNING] maven-surefire-plugin .. 2.4.2
> [INFO]
> [WARNING] Project does not define minimum Maven version, default is: 2.0
> [INFO] Plugins require minimum Maven version of: 3.0.5
> [INFO] Note: the super-pom from Maven 3.3.9 defines some of the plugin
> [INFO] versions and may be influencing the plugins required minimum
> Maven
> [INFO] version.
> [INFO]
> [ERROR] Project does not define required minimum version of Maven.
> [ERROR] Update the pom.xml to contain
> [ERROR]
> [ERROR] 3.0.5
> [ERROR]
> {noformat}
> As a fix we should
> # Specify version for all maven plugin in use
> # Specify minimum version of maven to be used (version used in CI is 3.2.1)
> # Configure enforcer plugin to ensure that in future no plugin is used
> without specifying the version [1]
> [1] http://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OAK-6826) Refactor Jcr class to remove dependency on o.a.j.oak.plugins.index
[ https://issues.apache.org/jira/browse/OAK-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Deparvu resolved OAK-6826. --- Resolution: Fixed Fix Version/s: 1.7.12 fixed with http://svn.apache.org/viewvc?rev=1815457=rev > Refactor Jcr class to remove dependency on o.a.j.oak.plugins.index > -- > > Key: OAK-6826 > URL: https://issues.apache.org/jira/browse/OAK-6826 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: jcr >Reporter: Alex Deparvu >Assignee: Alex Deparvu >Priority: Minor > Fix For: 1.7.12 > > > I'd like to take a look at the Jcr class, to have it rely more on api/spi > classes and reduce if possible references to oak-core impl. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (OAK-5455) Specify versions for maven plugins used in build for ensuring stable builds
[
https://issues.apache.org/jira/browse/OAK-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255295#comment-16255295
]
Julian Reschke edited comment on OAK-5455 at 11/16/17 2:24 PM:
---
trunk: [r1815458|http://svn.apache.org/r1815458]
[r1815449|http://svn.apache.org/r1815449]
was (Author: reschke):
trunk: [r1815449|http://svn.apache.org/r1815449]
> Specify versions for maven plugins used in build for ensuring stable builds
> ---
>
> Key: OAK-5455
> URL: https://issues.apache.org/jira/browse/OAK-5455
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: parent
>Reporter: Chetan Mehrotra
>Assignee: Julian Reschke
> Fix For: 1.8, 1.7.13
>
> Attachments: OAK-5455-v1.patch, enforce.diff
>
>
> Running a check for plugin versions used in oak build
> {noformat}
> mvn versions:display-plugin-updates
> {noformat}
> leads to following warning
> {noformat}
> [INFO] The following plugin updates are available:
> [INFO] org.apache.felix:maven-scr-plugin .. 1.16.0 -> 1.21.0
> [INFO]
> [WARNING] The following plugins do not have their version specified:
> [WARNING] maven-compiler-plugin .. 2.0.2
> [WARNING] maven-deploy-plugin . (from super-pom) 2.4
> [WARNING] maven-failsafe-plugin . 2.12.4
> [WARNING] maven-jar-plugin . 2.1
> [WARNING] maven-javadoc-plugin . 2.0
> [WARNING] maven-release-plugin . (from super-pom) 2.0-beta-4
> [WARNING] maven-resources-plugin ... 2.2
> [WARNING] maven-surefire-plugin .. 2.4.2
> [INFO]
> [WARNING] Project does not define minimum Maven version, default is: 2.0
> [INFO] Plugins require minimum Maven version of: 3.0.5
> [INFO] Note: the super-pom from Maven 3.3.9 defines some of the plugin
> [INFO] versions and may be influencing the plugins required minimum
> Maven
> [INFO] version.
> [INFO]
> [ERROR] Project does not define required minimum version of Maven.
> [ERROR] Update the pom.xml to contain
> [ERROR]
> [ERROR] 3.0.5
> [ERROR]
> {noformat}
> As a fix we should
> # Specify version for all maven plugin in use
> # Specify minimum version of maven to be used (version used in CI is 3.2.1)
> # Configure enforcer plugin to ensure that in future no plugin is used
> without specifying the version [1]
> [1] http://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OAK-6954) Build Jackrabbit Oak #982 failed
Hudson created OAK-6954: --- Summary: Build Jackrabbit Oak #982 failed Key: OAK-6954 URL: https://issues.apache.org/jira/browse/OAK-6954 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson No description is provided The build Jackrabbit Oak #982 has failed. First failed run: [Jackrabbit Oak #982|https://builds.apache.org/job/Jackrabbit%20Oak/982/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/982/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6741) Switch to official OSGi component and metatype annotations
[ https://issues.apache.org/jira/browse/OAK-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255303#comment-16255303 ] Marcel Reutegger commented on OAK-6741: --- I will reschedule this issue and all sub-tasks to 1.10. If anyone has time to work on these tasks feel free to assign it to you and resolve even in the 1.8 time frame. However, please be careful not to introduce regressions as there may be subtle differences. > Switch to official OSGi component and metatype annotations > -- > > Key: OAK-6741 > URL: https://issues.apache.org/jira/browse/OAK-6741 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Robert Munteanu > Fix For: 1.8, 1.7.12 > > Attachments: OAK-6741-proposed-changes-chetans-feedback.patch, > osgi-metadata-1.7.8.json, osgi-metadata-trunk.json > > > We should remove the 'old' Felix SCR annotations and move to the 'new' OSGi > R6 annotations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6741) Switch to official OSGi component and metatype annotations
[ https://issues.apache.org/jira/browse/OAK-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-6741: -- Fix Version/s: (was: 1.7.12) (was: 1.8) 1.10 > Switch to official OSGi component and metatype annotations > -- > > Key: OAK-6741 > URL: https://issues.apache.org/jira/browse/OAK-6741 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Robert Munteanu > Fix For: 1.10 > > Attachments: OAK-6741-proposed-changes-chetans-feedback.patch, > osgi-metadata-1.7.8.json, osgi-metadata-trunk.json > > > We should remove the 'old' Felix SCR annotations and move to the 'new' OSGi > R6 annotations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-5455) Specify versions for maven plugins used in build for ensuring stable builds
[
https://issues.apache.org/jira/browse/OAK-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255295#comment-16255295
]
Julian Reschke commented on OAK-5455:
-
trunk: [r1815449|http://svn.apache.org/r1815449]
> Specify versions for maven plugins used in build for ensuring stable builds
> ---
>
> Key: OAK-5455
> URL: https://issues.apache.org/jira/browse/OAK-5455
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: parent
>Reporter: Chetan Mehrotra
>Assignee: Julian Reschke
> Fix For: 1.8, 1.7.13
>
> Attachments: OAK-5455-v1.patch, enforce.diff
>
>
> Running a check for plugin versions used in oak build
> {noformat}
> mvn versions:display-plugin-updates
> {noformat}
> leads to following warning
> {noformat}
> [INFO] The following plugin updates are available:
> [INFO] org.apache.felix:maven-scr-plugin .. 1.16.0 -> 1.21.0
> [INFO]
> [WARNING] The following plugins do not have their version specified:
> [WARNING] maven-compiler-plugin .. 2.0.2
> [WARNING] maven-deploy-plugin . (from super-pom) 2.4
> [WARNING] maven-failsafe-plugin . 2.12.4
> [WARNING] maven-jar-plugin . 2.1
> [WARNING] maven-javadoc-plugin . 2.0
> [WARNING] maven-release-plugin . (from super-pom) 2.0-beta-4
> [WARNING] maven-resources-plugin ... 2.2
> [WARNING] maven-surefire-plugin .. 2.4.2
> [INFO]
> [WARNING] Project does not define minimum Maven version, default is: 2.0
> [INFO] Plugins require minimum Maven version of: 3.0.5
> [INFO] Note: the super-pom from Maven 3.3.9 defines some of the plugin
> [INFO] versions and may be influencing the plugins required minimum
> Maven
> [INFO] version.
> [INFO]
> [ERROR] Project does not define required minimum version of Maven.
> [ERROR] Update the pom.xml to contain
> [ERROR]
> [ERROR] 3.0.5
> [ERROR]
> {noformat}
> As a fix we should
> # Specify version for all maven plugin in use
> # Specify minimum version of maven to be used (version used in CI is 3.2.1)
> # Configure enforcer plugin to ensure that in future no plugin is used
> without specifying the version [1]
> [1] http://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6953) CacheLIRS cannot be disabled
[ https://issues.apache.org/jira/browse/OAK-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255292#comment-16255292 ] Marcel Reutegger commented on OAK-6953: --- Added ignored test: http://svn.apache.org/r1815450 > CacheLIRS cannot be disabled > > > Key: OAK-6953 > URL: https://issues.apache.org/jira/browse/OAK-6953 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 1.8 > > > The CacheLIRS cannot be disabled by setting the maxWeight to zero whereas the > Guava implementation can be disabled this way. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-1844) Verify resilience goals
[ https://issues.apache.org/jira/browse/OAK-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-1844: --- Fix Version/s: (was: 1.8) > Verify resilience goals > --- > > Key: OAK-1844 > URL: https://issues.apache.org/jira/browse/OAK-1844 > Project: Jackrabbit Oak > Issue Type: Epic >Reporter: Michael Dürig > Labels: resilience > > This is a container issue for verifying the resilience goals set out for Oak. > See https://wiki.apache.org/jackrabbit/Resilience for the work in progress of > such goals. Once we have an agreement on that, subtasks of this issue could > be used to track the verification process of each of the individual goals. > Discussion here: http://jackrabbit.markmail.org/thread/5cndir5sjrc5dtla -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OAK-6066) Migration of binaries relies on implementation details of the TarMK
[
https://issues.apache.org/jira/browse/OAK-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig reassigned OAK-6066:
--
Assignee: Tomek Rękawek
> Migration of binaries relies on implementation details of the TarMK
> ---
>
> Key: OAK-6066
> URL: https://issues.apache.org/jira/browse/OAK-6066
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: upgrade
>Reporter: Michael Dürig
>Assignee: Tomek Rękawek
> Labels: migration, tooling
> Fix For: 1.8
>
> Attachments: OAK_6066.patch
>
>
> This was uncovered with the work on OAK-6051.
> On {{NodeStore.merge()}} the TarMK uses {{SegmentNodeState#fastEquals}} to
> efficiently determine whether there is something to commit and whether the
> base state changed since the builder about to commit was acquired. For
> efficiency reasons {{fastEquals}} can return "false negatives". AFAIU
> migration of binaries depends on this implementation detail because without
> this optimisation migration fails. ({{SegmentToExternalMigrationTest}} and
> {{ExternalToExternalMigrationTest}} fail).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6066) Migration of binaries relies on implementation details of the TarMK
[
https://issues.apache.org/jira/browse/OAK-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255267#comment-16255267
]
Michael Dürig commented on OAK-6066:
[~tomek.rekawek], could you help triaging this one? Is this something that
needs to be addressed for 1.8? What is the risk of not doing anything?
> Migration of binaries relies on implementation details of the TarMK
> ---
>
> Key: OAK-6066
> URL: https://issues.apache.org/jira/browse/OAK-6066
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: upgrade
>Reporter: Michael Dürig
> Labels: migration, tooling
> Fix For: 1.8
>
> Attachments: OAK_6066.patch
>
>
> This was uncovered with the work on OAK-6051.
> On {{NodeStore.merge()}} the TarMK uses {{SegmentNodeState#fastEquals}} to
> efficiently determine whether there is something to commit and whether the
> base state changed since the builder about to commit was acquired. For
> efficiency reasons {{fastEquals}} can return "false negatives". AFAIU
> migration of binaries depends on this implementation detail because without
> this optimisation migration fails. ({{SegmentToExternalMigrationTest}} and
> {{ExternalToExternalMigrationTest}} fail).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5973) Metrics integration should expose endpoints in an non flat name space
[ https://issues.apache.org/jira/browse/OAK-5973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-5973: --- Fix Version/s: (was: 1.8) > Metrics integration should expose endpoints in an non flat name space > - > > Key: OAK-5973 > URL: https://issues.apache.org/jira/browse/OAK-5973 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Michael Dürig > Labels: monitoring, production > > The Metrics integration introduced with OAK-3654 exposes all endpoints in a > flat namespace. This quickly becomes troublesome as I would expect the number > of endpoints to quickly grow. We should come up with a way to expose them by > grouping related ones together. Preferably in a similar way loggers are > usually acquired and used to developers do not need to spend much time > thinking about naming issues when introducing new endpoints. At the same time > this would expose the endpoints in a way familiar from loggers. > Related discussion: > https://lists.apache.org/thread.html/a331f826d0767c501864426b48255a82b9e92f5d8582e9cf107745cf@%3Coak-dev.jackrabbit.apache.org%3E -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6756) Convert oak-auth-external to OSGi R6 annotations
[ https://issues.apache.org/jira/browse/OAK-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255260#comment-16255260 ] Christian Schneider commented on OAK-6756: -- Hi [~anchela], I have now removed the unnecessary changes and also rebased to current master. It would be great if you could review the current state. The build passes but I am not sure how well it tests for this highly OSGi related change. Is there a good way how I can validate if my changes work in OSGi? If it makes sense I can add some OSGi tests but I would need some help in the scope of such tests. Christian > Convert oak-auth-external to OSGi R6 annotations > > > Key: OAK-6756 > URL: https://issues.apache.org/jira/browse/OAK-6756 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: auth-external >Reporter: Robert Munteanu >Assignee: angela > Fix For: 1.10 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6911) Provide a way to tune inline size while storing binaries
[ https://issues.apache.org/jira/browse/OAK-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Dürig updated OAK-6911: --- Fix Version/s: (was: 1.8) > Provide a way to tune inline size while storing binaries > > > Key: OAK-6911 > URL: https://issues.apache.org/jira/browse/OAK-6911 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar >Reporter: Chetan Mehrotra > Labels: performance, scalability > > SegmentNodeStore currently inlines binaries of size less that 16KB > (Segment.MEDIUM_LIMIT) even if external BlobStore is configured. > Due to this behaviour quite a bit of segment tar storage consist of blob > data. In one setup out of 370 GB segmentstore size 290GB is due to inlined > binary. If most of this binary content is moved to BlobStore then it would > allow same repository to work better in lesser RAM > So it would be useful if some way is provided to disable this default > behaviour and let BlobStore take control of inline size i.e. in presence of > BlobStore no inlining is attempted by SegmentWriter. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OAK-6951) Add package export versions for oak-query-spi
[ https://issues.apache.org/jira/browse/OAK-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela reassigned OAK-6951: --- Assignee: Thomas Mueller (was: angela) [~tmueller], I am assigning this to you. > Add package export versions for oak-query-spi > - > > Key: OAK-6951 > URL: https://issues.apache.org/jira/browse/OAK-6951 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: core >Reporter: angela >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > Attachments: OAK-6951.patch > > > [~tmueller], as discussed on monday the public query SPI should come with > explicit version management. > I will provide a proposed patch. > cc: [~mreutegg] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OAK-6947) Add package export versions for oak-store-spi
[ https://issues.apache.org/jira/browse/OAK-6947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela reassigned OAK-6947: --- Assignee: Michael Dürig (was: angela) > Add package export versions for oak-store-spi > - > > Key: OAK-6947 > URL: https://issues.apache.org/jira/browse/OAK-6947 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: store-spi >Reporter: angela >Assignee: Michael Dürig > Fix For: 1.8 > > Attachments: OAK-6947.patch > > > [~mduerig], [~mreutegg], [~frm], [~stillalex], do you have any strong > preferences wrt to the packages we placed in the _oak-store-spi_ module? > Currently we explicitly export all packages and I think it would make sense > to enable the baseline plugin for these packages. > Any objection from your side? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6947) Add package export versions for oak-store-spi
[ https://issues.apache.org/jira/browse/OAK-6947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255249#comment-16255249 ] angela commented on OAK-6947: - [~mduerig], i am assigning this to you. > Add package export versions for oak-store-spi > - > > Key: OAK-6947 > URL: https://issues.apache.org/jira/browse/OAK-6947 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: store-spi >Reporter: angela >Assignee: Michael Dürig > Fix For: 1.8 > > Attachments: OAK-6947.patch > > > [~mduerig], [~mreutegg], [~frm], [~stillalex], do you have any strong > preferences wrt to the packages we placed in the _oak-store-spi_ module? > Currently we explicitly export all packages and I think it would make sense > to enable the baseline plugin for these packages. > Any objection from your side? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6941) Compatibility matrix for oak-run compact
[
https://issues.apache.org/jira/browse/OAK-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6941:
---
Labels: documentation tooling (was: )
> Compatibility matrix for oak-run compact
>
>
> Key: OAK-6941
> URL: https://issues.apache.org/jira/browse/OAK-6941
> Project: Jackrabbit Oak
> Issue Type: Documentation
> Components: doc, run, segment-tar
>Reporter: Valentin Olteanu
> Labels: documentation, tooling
> Fix For: 1.8
>
>
> h4. Problem statement
> For compacting the segmentstore using {{oak-run}}, the safest option is to
> use the same version of {{oak-run}} as the Oak version used to generate the
> repository. Yet, sometimes, a newer {{oak-run}} version is recommended to
> benefit of bug fixes and improvements, but not every combination of source
> repo and oak-run is safe to use and the user needs a way to check the
> compatibility. Thus, the users need a tool that guides the decision of which
> version to use.
> h4. Requirements
> * Easy to decide what {{oak-run}} version should be used for a certain Oak
> version
> * Up to date with the latest releases
> * Machine readable for scripting
> * Include details on the benefits of using a certain version (release notes)
> * Blacklist of versions that should not be used (with alternatives)
> h4. Solution
> TBD
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6941) Compatibility matrix for oak-run compact
[
https://issues.apache.org/jira/browse/OAK-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6941:
---
Component/s: doc
> Compatibility matrix for oak-run compact
>
>
> Key: OAK-6941
> URL: https://issues.apache.org/jira/browse/OAK-6941
> Project: Jackrabbit Oak
> Issue Type: Documentation
> Components: doc, run, segment-tar
>Reporter: Valentin Olteanu
> Fix For: 1.8
>
>
> h4. Problem statement
> For compacting the segmentstore using {{oak-run}}, the safest option is to
> use the same version of {{oak-run}} as the Oak version used to generate the
> repository. Yet, sometimes, a newer {{oak-run}} version is recommended to
> benefit of bug fixes and improvements, but not every combination of source
> repo and oak-run is safe to use and the user needs a way to check the
> compatibility. Thus, the users need a tool that guides the decision of which
> version to use.
> h4. Requirements
> * Easy to decide what {{oak-run}} version should be used for a certain Oak
> version
> * Up to date with the latest releases
> * Machine readable for scripting
> * Include details on the benefits of using a certain version (release notes)
> * Blacklist of versions that should not be used (with alternatives)
> h4. Solution
> TBD
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6941) Compatibility matrix for oak-run compact
[
https://issues.apache.org/jira/browse/OAK-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-6941:
---
Fix Version/s: 1.8
> Compatibility matrix for oak-run compact
>
>
> Key: OAK-6941
> URL: https://issues.apache.org/jira/browse/OAK-6941
> Project: Jackrabbit Oak
> Issue Type: Documentation
> Components: doc, run, segment-tar
>Reporter: Valentin Olteanu
> Fix For: 1.8
>
>
> h4. Problem statement
> For compacting the segmentstore using {{oak-run}}, the safest option is to
> use the same version of {{oak-run}} as the Oak version used to generate the
> repository. Yet, sometimes, a newer {{oak-run}} version is recommended to
> benefit of bug fixes and improvements, but not every combination of source
> repo and oak-run is safe to use and the user needs a way to check the
> compatibility. Thus, the users need a tool that guides the decision of which
> version to use.
> h4. Requirements
> * Easy to decide what {{oak-run}} version should be used for a certain Oak
> version
> * Up to date with the latest releases
> * Machine readable for scripting
> * Include details on the benefits of using a certain version (release notes)
> * Blacklist of versions that should not be used (with alternatives)
> h4. Solution
> TBD
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6826) Refactor Jcr class to remove dependency on o.a.j.oak.plugins.index
[ https://issues.apache.org/jira/browse/OAK-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255227#comment-16255227 ] Alex Deparvu commented on OAK-6826: --- ack. [~anchela] let me test this out against latest trunk and will apply the patch > Refactor Jcr class to remove dependency on o.a.j.oak.plugins.index > -- > > Key: OAK-6826 > URL: https://issues.apache.org/jira/browse/OAK-6826 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: jcr >Reporter: Alex Deparvu >Assignee: Alex Deparvu >Priority: Minor > > I'd like to take a look at the Jcr class, to have it rely more on api/spi > classes and reduce if possible references to oak-core impl. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6948) Build Jackrabbit Oak #977 failed
[ https://issues.apache.org/jira/browse/OAK-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255219#comment-16255219 ] Hudson commented on OAK-6948: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #981|https://builds.apache.org/job/Jackrabbit%20Oak/981/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/981/console] > Build Jackrabbit Oak #977 failed > > > Key: OAK-6948 > URL: https://issues.apache.org/jira/browse/OAK-6948 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #977 has failed. > First failed run: [Jackrabbit Oak > #977|https://builds.apache.org/job/Jackrabbit%20Oak/977/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/977/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-4887) Query cost estimation: ordering by an unindexed property not reflected
[ https://issues.apache.org/jira/browse/OAK-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-4887: Sprint: L15 > Query cost estimation: ordering by an unindexed property not reflected > -- > > Key: OAK-4887 > URL: https://issues.apache.org/jira/browse/OAK-4887 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Affects Versions: 1.4.2 >Reporter: Alexander Klimetschek >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > > A query that orders by an unindexed property seems to have no effect on the > cost estimation, compared to the same query without the order by, although it > has a big impact on the execution performance for larger results/indexes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-4887) Query cost estimation: ordering by an unindexed property not reflected
[ https://issues.apache.org/jira/browse/OAK-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved OAK-4887. - Resolution: Fixed > Query cost estimation: ordering by an unindexed property not reflected > -- > > Key: OAK-4887 > URL: https://issues.apache.org/jira/browse/OAK-4887 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Affects Versions: 1.4.2 >Reporter: Alexander Klimetschek >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > > A query that orders by an unindexed property seems to have no effect on the > cost estimation, compared to the same query without the order by, although it > has a big impact on the execution performance for larger results/indexes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-4887) Query cost estimation: ordering by an unindexed property not reflected
[ https://issues.apache.org/jira/browse/OAK-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255158#comment-16255158 ] Thomas Mueller commented on OAK-4887: - http://svn.apache.org/r1815440 (trunk) > Query cost estimation: ordering by an unindexed property not reflected > -- > > Key: OAK-4887 > URL: https://issues.apache.org/jira/browse/OAK-4887 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Affects Versions: 1.4.2 >Reporter: Alexander Klimetschek >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > > A query that orders by an unindexed property seems to have no effect on the > cost estimation, compared to the same query without the order by, although it > has a big impact on the execution performance for larger results/indexes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-4887) Query cost estimation: ordering by an unindexed property not reflected
[ https://issues.apache.org/jira/browse/OAK-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255157#comment-16255157 ] Thomas Mueller commented on OAK-4887: - Even without the patch, with current trunk, the right index is used (if there are two indexes as described above). This is because the Lucene index returns a lower cost if "order by" of that property is supported by the index (I think each indexed property reduces the cost of the index). However, with the patch, the limit is used correctly to adjust the cost. > Query cost estimation: ordering by an unindexed property not reflected > -- > > Key: OAK-4887 > URL: https://issues.apache.org/jira/browse/OAK-4887 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Affects Versions: 1.4.2 >Reporter: Alexander Klimetschek >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > > A query that orders by an unindexed property seems to have no effect on the > cost estimation, compared to the same query without the order by, although it > has a big impact on the execution performance for larger results/indexes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-4887) Query cost estimation: ordering by an unindexed property not reflected
[ https://issues.apache.org/jira/browse/OAK-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-4887: Fix Version/s: 1.7.12 > Query cost estimation: ordering by an unindexed property not reflected > -- > > Key: OAK-4887 > URL: https://issues.apache.org/jira/browse/OAK-4887 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: query >Affects Versions: 1.4.2 >Reporter: Alexander Klimetschek >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > > A query that orders by an unindexed property seems to have no effect on the > cost estimation, compared to the same query without the order by, although it > has a big impact on the execution performance for larger results/indexes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6936) use current Tika version 1.16
[ https://issues.apache.org/jira/browse/OAK-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255142#comment-16255142 ] Julian Reschke commented on OAK-6936: - trunk: [r1815439|http://svn.apache.org/r1815439] > use current Tika version 1.16 > - > > Key: OAK-6936 > URL: https://issues.apache.org/jira/browse/OAK-6936 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_6 > Fix For: 1.8, 1.7.12 > > Attachments: OAK-6936.diff > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6936) use current Tika version 1.16
[ https://issues.apache.org/jira/browse/OAK-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-6936. - Resolution: Fixed Fix Version/s: 1.7.12 > use current Tika version 1.16 > - > > Key: OAK-6936 > URL: https://issues.apache.org/jira/browse/OAK-6936 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_6 > Fix For: 1.8, 1.7.12 > > Attachments: OAK-6936.diff > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6936) use current Tika version 1.16
[ https://issues.apache.org/jira/browse/OAK-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6936: Labels: candidate_oak_1_6 (was: ) > use current Tika version 1.16 > - > > Key: OAK-6936 > URL: https://issues.apache.org/jira/browse/OAK-6936 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_6 > Fix For: 1.8, 1.7.12 > > Attachments: OAK-6936.diff > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6952) add SHA512 checksums to releases
[ https://issues.apache.org/jira/browse/OAK-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255133#comment-16255133 ] Julian Reschke commented on OAK-6952: - Done in trunk with trunk: [r1815438|http://svn.apache.org/r1815438] - will backport once 1.7.12 release was successful. > add SHA512 checksums to releases > > > Key: OAK-6952 > URL: https://issues.apache.org/jira/browse/OAK-6952 > Project: Jackrabbit Oak > Issue Type: Task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, > candidate_oak_1_6 > Fix For: 1.8, 1.7.12 > > > http://www.apache.org/dev/release-distribution#sigs-and-sums > "The checksum SHOULD be generated using SHA-512. A .sha file SHOULD contain a > SHA-1 checksum, for historical reasons." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6952) add SHA512 checksums to releases
[ https://issues.apache.org/jira/browse/OAK-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-6952. - Resolution: Fixed Fix Version/s: 1.7.12 > add SHA512 checksums to releases > > > Key: OAK-6952 > URL: https://issues.apache.org/jira/browse/OAK-6952 > Project: Jackrabbit Oak > Issue Type: Task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, > candidate_oak_1_6 > Fix For: 1.8, 1.7.12 > > > http://www.apache.org/dev/release-distribution#sigs-and-sums > "The checksum SHOULD be generated using SHA-512. A .sha file SHOULD contain a > SHA-1 checksum, for historical reasons." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6948) Build Jackrabbit Oak #977 failed
[ https://issues.apache.org/jira/browse/OAK-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255129#comment-16255129 ] Hudson commented on OAK-6948: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #980|https://builds.apache.org/job/Jackrabbit%20Oak/980/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/980/console] > Build Jackrabbit Oak #977 failed > > > Key: OAK-6948 > URL: https://issues.apache.org/jira/browse/OAK-6948 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #977 has failed. > First failed run: [Jackrabbit Oak > #977|https://builds.apache.org/job/Jackrabbit%20Oak/977/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/977/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6952) add SHA512 checksums to releases
[ https://issues.apache.org/jira/browse/OAK-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6952: Component/s: (was: parent) > add SHA512 checksums to releases > > > Key: OAK-6952 > URL: https://issues.apache.org/jira/browse/OAK-6952 > Project: Jackrabbit Oak > Issue Type: Task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, > candidate_oak_1_6 > Fix For: 1.8 > > > http://www.apache.org/dev/release-distribution#sigs-and-sums > "The checksum SHOULD be generated using SHA-512. A .sha file SHOULD contain a > SHA-1 checksum, for historical reasons." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6953) CacheLIRS cannot be disabled
Marcel Reutegger created OAK-6953: - Summary: CacheLIRS cannot be disabled Key: OAK-6953 URL: https://issues.apache.org/jira/browse/OAK-6953 Project: Jackrabbit Oak Issue Type: Bug Components: documentmk Reporter: Marcel Reutegger Assignee: Marcel Reutegger Priority: Minor Fix For: 1.8 The CacheLIRS cannot be disabled by setting the maxWeight to zero whereas the Guava implementation can be disabled this way. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-5194) 'Dynamic' Automembership should respect both User and Group Config Values
[
https://issues.apache.org/jira/browse/OAK-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved OAK-5194.
-
Resolution: Fixed
Fix Version/s: 1.7.12
[~stillalex], i committed the fix at revision 1815434. maybe you want to take a
look...
> 'Dynamic' Automembership should respect both User and Group Config Values
> -
>
> Key: OAK-5194
> URL: https://issues.apache.org/jira/browse/OAK-5194
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: auth-external
>Reporter: angela
>Assignee: angela
> Fix For: 1.8, 1.7.12
>
>
> Currently the {{ExternalPrincipalConfiguration}} evaluates
> {{group.autoMembership}} configuration parameter to determine the
> automembership of a given external user but ignores the
> {{user.autoMembership}} configuration.
> IMHO it should respect both values and have the {{PrincipalProvider}} act
> accordingly:
> - retrieving group principals for a user-principal should include boths
> - retrieving group principals for a group-principal should be added and
> return the configured group.autoMembership
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (OAK-6860) RDB*Store: update Derby to release 10.14
[ https://issues.apache.org/jira/browse/OAK-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255016#comment-16255016 ] Julian Reschke edited comment on OAK-6860 at 11/16/17 10:35 AM: trunk: [r1815426|http://svn.apache.org/r1815426] 1.6: [r1815433|http://svn.apache.org/r1815433] was (Author: reschke): trunk: [r1815426|http://svn.apache.org/r1815426] > RDB*Store: update Derby to release 10.14 > > > Key: OAK-6860 > URL: https://issues.apache.org/jira/browse/OAK-6860 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.8, 1.7.12, 1.6.7 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6826) Refactor Jcr class to remove dependency on o.a.j.oak.plugins.index
[ https://issues.apache.org/jira/browse/OAK-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255091#comment-16255091 ] angela commented on OAK-6826: - [~stillalex], I would appreciate if we could get this issue resolved today, such that I can clean up the exports that are no longer needed in _oak-core_. > Refactor Jcr class to remove dependency on o.a.j.oak.plugins.index > -- > > Key: OAK-6826 > URL: https://issues.apache.org/jira/browse/OAK-6826 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: jcr >Reporter: Alex Deparvu >Assignee: Alex Deparvu >Priority: Minor > > I'd like to take a look at the Jcr class, to have it rely more on api/spi > classes and reduce if possible references to oak-core impl. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6860) RDB*Store: update Derby to release 10.14
[ https://issues.apache.org/jira/browse/OAK-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6860: Fix Version/s: 1.6.7 > RDB*Store: update Derby to release 10.14 > > > Key: OAK-6860 > URL: https://issues.apache.org/jira/browse/OAK-6860 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.8, 1.7.12, 1.6.7 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6860) RDB*Store: update Derby to release 10.14
[ https://issues.apache.org/jira/browse/OAK-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6860: Labels: (was: candidate_oak_1_6) > RDB*Store: update Derby to release 10.14 > > > Key: OAK-6860 > URL: https://issues.apache.org/jira/browse/OAK-6860 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.8, 1.7.12, 1.6.7 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6952) add SHA512 checksums to releases
[ https://issues.apache.org/jira/browse/OAK-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6952: Labels: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4 candidate_oak_1_6 (was: ) > add SHA512 checksums to releases > > > Key: OAK-6952 > URL: https://issues.apache.org/jira/browse/OAK-6952 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, > candidate_oak_1_6 > Fix For: 1.8 > > > http://www.apache.org/dev/release-distribution#sigs-and-sums > "The checksum SHOULD be generated using SHA-512. A .sha file SHOULD contain a > SHA-1 checksum, for historical reasons." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OAK-6952) add SHA512 checksums to releases
Julian Reschke created OAK-6952: --- Summary: add SHA512 checksums to releases Key: OAK-6952 URL: https://issues.apache.org/jira/browse/OAK-6952 Project: Jackrabbit Oak Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Priority: Minor http://www.apache.org/dev/release-distribution#sigs-and-sums "The checksum SHOULD be generated using SHA-512. A .sha file SHOULD contain a SHA-1 checksum, for historical reasons." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-6952) add SHA512 checksums to releases
[ https://issues.apache.org/jira/browse/OAK-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-6952: Fix Version/s: 1.8 > add SHA512 checksums to releases > > > Key: OAK-6952 > URL: https://issues.apache.org/jira/browse/OAK-6952 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 1.8 > > > http://www.apache.org/dev/release-distribution#sigs-and-sums > "The checksum SHOULD be generated using SHA-512. A .sha file SHOULD contain a > SHA-1 checksum, for historical reasons." -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6221) Deprecate SecurityProviderImpl
[
https://issues.apache.org/jira/browse/OAK-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255085#comment-16255085
]
angela commented on OAK-6221:
-
[~stillalex], any chance we could get that into the 1.8 release?
> Deprecate SecurityProviderImpl
> --
>
> Key: OAK-6221
> URL: https://issues.apache.org/jira/browse/OAK-6221
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, security
>Reporter: Alex Deparvu
>Assignee: Alex Deparvu
>
> As agreed on OAK-6172, the {{SecurityProviderImpl}} should be deprecated in
> favor of the {{InternalSecurityProvider}}.
> This should also cover coming up with a way to use the new version in tests
> while we figure out OSGi testing setups.
> fyi [~anchela]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-6381) Improved index analysis tools
[ https://issues.apache.org/jira/browse/OAK-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated OAK-6381: Fix Version/s: 1.7.12 > Improved index analysis tools > - > > Key: OAK-6381 > URL: https://issues.apache.org/jira/browse/OAK-6381 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Thomas Mueller >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > > It would be good to have more tools to analyze indexes: > * For Lucene indexes, get a histogram of samples (terms). We have > "getFieldInfo", which shows which fields are how common, but we don't have > terms. For example the /oak:index/lucene index contains 1 million fulltext > fields and node names for 1 million nodes, but I wonder why, and what typical > nodes names are, and maybe fulltext for most nodes is actually empty. Maybe a > new method "getTermHistogram(int sampleCount)" or similar > * For property indexes, number of updated nodes per second or so. Right now > we can just analyze the counts per key, but some indexes / keys are very > volatile (see many short lived entries) > * For Lucene indexes, writes per second or so (in MB). > * How indexes are used (approximate read nodes / MB per hours) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6381) Improved index analysis tools
[ https://issues.apache.org/jira/browse/OAK-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved OAK-6381. - Resolution: Fixed > Improved index analysis tools > - > > Key: OAK-6381 > URL: https://issues.apache.org/jira/browse/OAK-6381 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Thomas Mueller >Assignee: Thomas Mueller > Fix For: 1.8, 1.7.12 > > > It would be good to have more tools to analyze indexes: > * For Lucene indexes, get a histogram of samples (terms). We have > "getFieldInfo", which shows which fields are how common, but we don't have > terms. For example the /oak:index/lucene index contains 1 million fulltext > fields and node names for 1 million nodes, but I wonder why, and what typical > nodes names are, and maybe fulltext for most nodes is actually empty. Maybe a > new method "getTermHistogram(int sampleCount)" or similar > * For property indexes, number of updated nodes per second or so. Right now > we can just analyze the counts per key, but some indexes / keys are very > volatile (see many short lived entries) > * For Lucene indexes, writes per second or so (in MB). > * How indexes are used (approximate read nodes / MB per hours) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6946) org.apache.jackrabbit.oak.security.authentication.ldap must not be exported / filtered in parent
[
https://issues.apache.org/jira/browse/OAK-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255056#comment-16255056
]
angela commented on OAK-6946:
-
[~jsedding], yes... i know that... what confused me was the fact that the empty
parent package was explicitly mentioned in the baseline-filter in parent/pom.xml
> org.apache.jackrabbit.oak.security.authentication.ldap must not be exported /
> filtered in parent
>
>
> Key: OAK-6946
> URL: https://issues.apache.org/jira/browse/OAK-6946
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: auth-ldap
>Reporter: angela
>Assignee: angela
> Fix For: 1.8, 1.7.12
>
> Attachments: OAK-6946.patch
>
>
> The _org.apache.jackrabbit.oak.security.authentication.ldap_ package space is
> empty and there is nothing we plan to export there as the whole
> _oak-auth-ldap_ module just contains an implementation of the external-IDP
> API.
> Since the _maven-bundle-plugin_ doesn't have explicit {{}}
> instructions the plugin uses the default and thus (unintended by us) exports
> the _org.apache.jackrabbit.oak.security.authentication.ldap_ package.
> [~stillalex], fyi
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6381) Improved index analysis tools
[ https://issues.apache.org/jira/browse/OAK-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255057#comment-16255057 ] Thomas Mueller commented on OAK-6381: - http://svn.apache.org/r1815428 (trunk) getFieldTermInfo(String indexPath, String field, String term) > Improved index analysis tools > - > > Key: OAK-6381 > URL: https://issues.apache.org/jira/browse/OAK-6381 > Project: Jackrabbit Oak > Issue Type: Improvement >Reporter: Thomas Mueller >Assignee: Thomas Mueller > Fix For: 1.8 > > > It would be good to have more tools to analyze indexes: > * For Lucene indexes, get a histogram of samples (terms). We have > "getFieldInfo", which shows which fields are how common, but we don't have > terms. For example the /oak:index/lucene index contains 1 million fulltext > fields and node names for 1 million nodes, but I wonder why, and what typical > nodes names are, and maybe fulltext for most nodes is actually empty. Maybe a > new method "getTermHistogram(int sampleCount)" or similar > * For property indexes, number of updated nodes per second or so. Right now > we can just analyze the counts per key, but some indexes / keys are very > volatile (see many short lived entries) > * For Lucene indexes, writes per second or so (in MB). > * How indexes are used (approximate read nodes / MB per hours) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6946) org.apache.jackrabbit.oak.security.authentication.ldap must not be exported / filtered in parent
[
https://issues.apache.org/jira/browse/OAK-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255052#comment-16255052
]
Julian Sedding commented on OAK-6946:
-
FYI, the {{maven-bundle-plugin}} implicitly does not export any packages called
"impl" or "internal" and their descendant packages. That's why we're fine here.
> org.apache.jackrabbit.oak.security.authentication.ldap must not be exported /
> filtered in parent
>
>
> Key: OAK-6946
> URL: https://issues.apache.org/jira/browse/OAK-6946
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: auth-ldap
>Reporter: angela
>Assignee: angela
> Fix For: 1.8, 1.7.12
>
> Attachments: OAK-6946.patch
>
>
> The _org.apache.jackrabbit.oak.security.authentication.ldap_ package space is
> empty and there is nothing we plan to export there as the whole
> _oak-auth-ldap_ module just contains an implementation of the external-IDP
> API.
> Since the _maven-bundle-plugin_ doesn't have explicit {{}}
> instructions the plugin uses the default and thus (unintended by us) exports
> the _org.apache.jackrabbit.oak.security.authentication.ldap_ package.
> [~stillalex], fyi
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (OAK-6860) RDB*Store: update Derby to release 10.14
[ https://issues.apache.org/jira/browse/OAK-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255016#comment-16255016 ] Julian Reschke commented on OAK-6860: - trunk: [r1815426|http://svn.apache.org/r1815426] > RDB*Store: update Derby to release 10.14 > > > Key: OAK-6860 > URL: https://issues.apache.org/jira/browse/OAK-6860 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_6 > Fix For: 1.8, 1.7.12 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OAK-6860) RDB*Store: update Derby to release 10.14
[ https://issues.apache.org/jira/browse/OAK-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved OAK-6860. - Resolution: Fixed Fix Version/s: 1.7.12 > RDB*Store: update Derby to release 10.14 > > > Key: OAK-6860 > URL: https://issues.apache.org/jira/browse/OAK-6860 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: rdbmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_oak_1_6 > Fix For: 1.8, 1.7.12 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OAK-6948) Build Jackrabbit Oak #977 failed
[ https://issues.apache.org/jira/browse/OAK-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255007#comment-16255007 ] Hudson commented on OAK-6948: - Previously failing build now is OK. Passed run: [Jackrabbit Oak #979|https://builds.apache.org/job/Jackrabbit%20Oak/979/] [console log|https://builds.apache.org/job/Jackrabbit%20Oak/979/console] > Build Jackrabbit Oak #977 failed > > > Key: OAK-6948 > URL: https://issues.apache.org/jira/browse/OAK-6948 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > No description is provided > The build Jackrabbit Oak #977 has failed. > First failed run: [Jackrabbit Oak > #977|https://builds.apache.org/job/Jackrabbit%20Oak/977/] [console > log|https://builds.apache.org/job/Jackrabbit%20Oak/977/console] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-3767) Provide a way to extend shipped index definitions
[
https://issues.apache.org/jira/browse/OAK-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-3767:
--
Fix Version/s: (was: 1.8)
1.10
> Provide a way to extend shipped index definitions
> -
>
> Key: OAK-3767
> URL: https://issues.apache.org/jira/browse/OAK-3767
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: indexing, query
>Reporter: Davide Giannella
> Fix For: 1.10
>
>
> We need to provide an explicit support for extending out of the box shipped
> index definition by an application built on top of Oak. Consider a Sling
> based app which ships with an index on assets like /oak:index/assetIndex.
> This application is now used in a project where some project specific
> extensions are to be done i.e. some new custom asset properties are to be
> indexed. Currently there are two options
> # Create new duplicate index - For project usage we can create a separate
> index which includes the project specific properties. This has following
> downsides
> ## Increases index memory consumption - As both /oak:index/assetIndex and
> /oak:index/myAssetIndex would index same asset nodes they would be storing
> the same asset path twice and hence cause an increase in memory consumption
> by the index
> # Increase in indexing time - With increase in number of indexes at same
> level the indexing time would increase
> # Ambiguity in index selection - As both indexes index same type of nodes
> they would compete in answering queries related to assets leading to
> ambiguity in index selection by query engine.
> Given above it would be better to avoid such cases and provide an explicit
> support for extending the index definitions. This can be done by enabling
> support for adding index definition extensions under a sub directory in a sub
> directory under /oak:index
> {noformat}
> /oak:index
> + assetIndex
> + apps
> + assetIndex
> {noformat}
> The indexing logic should then use the effective index definition for
> indexing and querying.
> *question*. Shall we allow this only under root or under any arbitrary path
> as well? For example /content.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (OAK-6947) Add package export versions for oak-store-spi
[ https://issues.apache.org/jira/browse/OAK-6947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reassigned OAK-6947: - Assignee: angela > Add package export versions for oak-store-spi > - > > Key: OAK-6947 > URL: https://issues.apache.org/jira/browse/OAK-6947 > Project: Jackrabbit Oak > Issue Type: Technical task > Components: store-spi >Reporter: angela >Assignee: angela > Fix For: 1.8 > > Attachments: OAK-6947.patch > > > [~mduerig], [~mreutegg], [~frm], [~stillalex], do you have any strong > preferences wrt to the packages we placed in the _oak-store-spi_ module? > Currently we explicitly export all packages and I think it would make sense > to enable the baseline plugin for these packages. > Any objection from your side? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OAK-4934) Query shapes for JCR Query
[
https://issues.apache.org/jira/browse/OAK-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller updated OAK-4934:
Fix Version/s: (was: 1.8)
1.10
> Query shapes for JCR Query
> --
>
> Key: OAK-4934
> URL: https://issues.apache.org/jira/browse/OAK-4934
> Project: Jackrabbit Oak
> Issue Type: Wish
> Components: query
>Reporter: Chetan Mehrotra
> Fix For: 1.10
>
>
> For certain requirements it would be good to have a notion/support to deduce
> query shape [1]
> {quote}
> A combination of query predicate, sort, and projection specifications.
> For the query predicate, only the structure of the predicate, including the
> field names, are significant; the values in the query predicate are
> insignificant. As such, a query predicate \{ type: 'food' \} is equivalent to
> the query predicate \{ type: 'utensil' \} for a query shape.
> {quote}
> So transforming that to Oak the shape should represent a JCR-SQL2 query
> string (xpath query gets transformed to SQL2) which is a *canonical*
> representation of actual query ignoring the property restriction values.
> Example we have 2 queries
> * SELECT * FROM [app:Asset] AS a WHERE a.[jcr:content/metadata/status] =
> 'published'
> * SELECT * FROM [app:Asset] AS a WHERE a.[jcr:content/metadata/status] =
> 'disabled'
> The query shape would be
> SELECT * FROM [app:Asset] AS a WHERE a.[jcr:content/metadata/status] = 'A'.
> The plan for query having given shape would remain same irrespective of value
> of property restrictions. Path restriction can cause some difference though
> The shape can then be used for
> * Stats Collection - Currently stats collection gets overflown if same query
> with different value gets invoked
> * Allow configuring hints - See support in Mongo [2] for an example. One
> specify via config that for a query of such and such shape this index should
> be used
> * Less noisy diagnostics - If a query gets invoked with bad plan the QE can
> log the warning once instead of logging it for each query invocation
> involving different values.
> [1] https://docs.mongodb.com/manual/reference/glossary/#term-query-shape
> [2] https://docs.mongodb.com/manual/reference/command/planCacheSetFilter/
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OAK-5488) BackgroundObserver MBean report Listener class again
[
https://issues.apache.org/jira/browse/OAK-5488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-5488:
--
Fix Version/s: (was: 1.8)
1.10
> BackgroundObserver MBean report Listener class again
>
>
> Key: OAK-5488
> URL: https://issues.apache.org/jira/browse/OAK-5488
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, jcr
>Affects Versions: 1.5.18
>Reporter: Stefan Eissing
>Priority: Minor
> Fix For: 1.10
>
>
> The MBean stats for {{BackgroundObserverStats}} used to give the className of
> the listening class.
> With the introduction of {{FilteringDispatcher}} all MBeans only list that
> class name, making it difficult to find out which observer really is shown.
> Proposal: show the effective className as before again.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (OAK-2556) Intermediate commit during async indexing
[ https://issues.apache.org/jira/browse/OAK-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reassigned OAK-2556: - Assignee: Thomas Mueller > Intermediate commit during async indexing > - > > Key: OAK-2556 > URL: https://issues.apache.org/jira/browse/OAK-2556 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene >Affects Versions: 1.0.11 >Reporter: Stefan Egli >Assignee: Thomas Mueller > Labels: resilience > Fix For: 1.10 > > > A recent issue found at a customer unveils a potential issue with the async > indexer. Reading the AsyncIndexUpdate.updateIndex it looks like it is doing > the entire update of the async indexer *in one go*, ie in one commit. > When there is - for some reason - however, a huge diff that the async indexer > has to process, the 'one big commit' can become gigantic. There is no limit > to the size of the commit in fact. > So the suggestion is to do intermediate commits while the async indexer is > going on. The reason this is acceptable is the fact that by doing async > indexing, that index is anyway not 100% up-to-date - so it would not make > much of a difference if it would commit after every 100 or 1000 changes > either. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
