Re: [VOTE] Release Apache Sling Repoinit JCR 1.1.50
+1 Regards, Eric On Tue, Jun 4, 2024 at 6:27 AM Julian Sedding wrote: > Hi, > > We solved 1 issue in this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12354758=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2864/ > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2864 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Regards > Julian >
Re: [VOTE] Release Apache Sling API 2.27.4
0 for me. It is probably ok, but I wasn't able to try it in the starter (or my own projects) due to the errors below from the feature analyzer, Maybe you can update and release those other impacted bundles at the same time as this one? [ERROR] [bundle-packages] org.apache.sling:org.apache.sling.scripting.core:2.4.8: Bundle is importing package org.apache.sling.api.scripting;version=[2.5,2.6) with start order 20 but no bundle is exporting these for that start order in the required version range. [ERROR] [bundle-packages] org.apache.sling:org.apache.sling.servlets.resolver:2.11.2: Bundle is importing package org.apache.sling.api.scripting;version=[2.5,2.6) with start order 20 but no bundle is exporting these for that start order in the required version range. Regards, Eric On Tue, Jun 4, 2024 at 6:25 AM Jörg Hoh wrote: > We solved 9 issues in this > release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353245=Text=12310710 > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2865/ > > You can use this UNIX script to download the release and verify the > signatures: > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > Usage: > sh check_staged_release.sh 2865 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > > > -- > https://cqdump.joerghoh.de >
Re: [VOTE] Release Apache Sling Engine 2.15.16
+1 Regards, Eric On Tue, May 28, 2024 at 8:00 AM Jörg Hoh wrote: > Hi, > > We solved 5 issues in this > release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12354681=Text > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2863/ > > You can use this UNIX script to download the release and verify the > signatures: > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > Usage: > sh check_staged_release.sh 2863 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours5 > > Jörg > > -- > https://cqdump.joerghoh.de >
[jira] [Updated] (SLING-12313) bump oak.version to 1.62.0 for compatibility
[
https://issues.apache.org/jira/browse/SLING-12313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman updated SLING-12313:
Summary: bump oak.version to 1.62.0 for compatibility (was: bump
oak.version 1.62.0 for compatibility)
> bump oak.version to 1.62.0 for compatibility
>
>
> Key: SLING-12313
> URL: https://issues.apache.org/jira/browse/SLING-12313
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: JCR Oak Server 1.4.2
>
>
> Oak 1.62.0 has bumped the version of the shaded guava packages to a new major
> version (from 32 to 33) which results in a failure to resolve the
> o.a.sling.jcr.oak.server bundle with that version of the Oak bundles.
> {code:java}
> org.osgi.framework.BundleException: Unable to resolve
> org.apache.sling.jcr.oak.server [144](R 144.0): missing requirement
> [org.apache.sling.jcr.oak.server [144](R 144.0)] osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.jackrabbit.guava.common.base)(version>=32.1.0)(!(version>=33.0.0)))
> Unresolved requirements: [[org.apache.sling.jcr.oak.server [144](R 144.0)]
> osgi.wiring.package;
> (&(osgi.wiring.package=org.apache.jackrabbit.guava.common.base)(version>=32.1.0)(!(version>=33.0.0)))]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SLING-12313) bump oak.version 1.62.0 for compatibility
Eric Norman created SLING-12313:
---
Summary: bump oak.version 1.62.0 for compatibility
Key: SLING-12313
URL: https://issues.apache.org/jira/browse/SLING-12313
Project: Sling
Issue Type: Improvement
Reporter: Eric Norman
Assignee: Eric Norman
Fix For: JCR Oak Server 1.4.2
Oak 1.62.0 has bumped the version of the shaded guava packages to a new major
version (from 32 to 33) which results in a failure to resolve the
o.a.sling.jcr.oak.server bundle with that version of the Oak bundles.
{code:java}
org.osgi.framework.BundleException: Unable to resolve
org.apache.sling.jcr.oak.server [144](R 144.0): missing requirement
[org.apache.sling.jcr.oak.server [144](R 144.0)] osgi.wiring.package;
(&(osgi.wiring.package=org.apache.jackrabbit.guava.common.base)(version>=32.1.0)(!(version>=33.0.0)))
Unresolved requirements: [[org.apache.sling.jcr.oak.server [144](R 144.0)]
osgi.wiring.package;
(&(osgi.wiring.package=org.apache.jackrabbit.guava.common.base)(version>=32.1.0)(!(version>=33.0.0)))]
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SLING-12312) add jakarta.servlet support in RequestLocaleResolver
Eric Norman created SLING-12312: --- Summary: add jakarta.servlet support in RequestLocaleResolver Key: SLING-12312 URL: https://issues.apache.org/jira/browse/SLING-12312 Project: Sling Issue Type: Improvement Reporter: Eric Norman Assignee: Eric Norman Fix For: i18n 2.6.4 provide a variant of the RequestLocaleResolver#resolveLocale call that accepts a jakarta.servlet.http.HttpServletRequest for use cases that have migrated to EE9 or later. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-12310) Fix test compatibility with java 17
[
https://issues.apache.org/jira/browse/SLING-12310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-12310.
-
Resolution: Fixed
Merged PR at:
[{{7437226}}|https://github.com/apache/sling-org-apache-sling-i18n/commit/7437226790f34737f29c1e99fa219afdde9d44ad]
> Fix test compatibility with java 17
> ---
>
> Key: SLING-12310
> URL: https://issues.apache.org/jira/browse/SLING-12310
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: i18n 2.6.4
>
>
> Some of the tests are failing when building with java 17.
> * bump oak/jackrabbit dependencies to the oldest still supported and
> compatible version
> * replace powermock usage with mockito
> * replace dependency on org.apache.sling.commons.testing with sling mocks
> equivalent
> * update various dependency versions to compatible versions
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SLING-12310) Fix test compatibility with java 17
Eric Norman created SLING-12310: --- Summary: Fix test compatibility with java 17 Key: SLING-12310 URL: https://issues.apache.org/jira/browse/SLING-12310 Project: Sling Issue Type: Improvement Reporter: Eric Norman Assignee: Eric Norman Fix For: i18n 2.6.4 Some of the tests are failing when building with java 17. * bump oak/jackrabbit dependencies to the oldest still supported and compatible version * replace powermock usage with mockito * replace dependency on org.apache.sling.commons.testing with sling mocks equivalent * update various dependency versions to compatible versions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SLING-12300) Provide a way to retrieve a JCR backed resource by its node identifier
[
https://issues.apache.org/jira/browse/SLING-12300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839407#comment-17839407
]
Eric Norman commented on SLING-12300:
-
[~paul.bjorkstrand] It offends me that you and [~radu] continue to trivialize
my concerns as "security by obscurity". That is not my argument and it never
was, so please stop doing that.
> Provide a way to retrieve a JCR backed resource by its node identifier
> --
>
> Key: SLING-12300
> URL: https://issues.apache.org/jira/browse/SLING-12300
> Project: Sling
> Issue Type: New Feature
> Components: JCR
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: JCR Resource 3.3.0
>
>
> Since all {{javax.jcr.Nodes}} have an identifier [0], a useful feature would
> be {{Resource}} retrieval by node id, which could be its {{jcr:uuid}}
> property for referenceable nodes or the path. In systems that would like to
> use UUID addressing, this would reduce the need for executing JCR queries for
> resource retrieval and would avoid double-reads via the JCR and then Sling
> API to obtain the resource.
> In order to provide a unified behaviour, paths starting with the {{/jcr:id/}}
> prefix should use the resource retrieval by node identifier.
> [0] -
> https://javadoc.io/static/javax.jcr/jcr/2.0/javax/jcr/Node.html#getIdentifier()
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (SLING-12300) Provide a way to retrieve a JCR backed resource by its node identifier
[
https://issues.apache.org/jira/browse/SLING-12300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839155#comment-17839155
]
Eric Norman edited comment on SLING-12300 at 4/19/24 11:40 PM:
---
[~radu] I know how long a UUID value is, how it is formatted and what
characters are allowed in there. That is a much smaller universe then all the
possible paths that may exist.
I still haven't seen a good reason why this is needed.
was (Author: enorman):
[~radu] I know how long a UUID value is, how it is formatted and what
characters are allowed in there. That is a much smaller universe then all the
possible paths that may exist.
I still having seen a good reason why this is needed.
> Provide a way to retrieve a JCR backed resource by its node identifier
> --
>
> Key: SLING-12300
> URL: https://issues.apache.org/jira/browse/SLING-12300
> Project: Sling
> Issue Type: New Feature
> Components: JCR
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: JCR Resource 3.3.0
>
>
> Since all {{javax.jcr.Nodes}} have an identifier [0], a useful feature would
> be {{Resource}} retrieval by node id, which could be its {{jcr:uuid}}
> property for referenceable nodes or the path. In systems that would like to
> use UUID addressing, this would reduce the need for executing JCR queries for
> resource retrieval and would avoid double-reads via the JCR and then Sling
> API to obtain the resource.
> In order to provide a unified behaviour, paths starting with the {{/jcr:id/}}
> prefix should use the resource retrieval by node identifier.
> [0] -
> https://javadoc.io/static/javax.jcr/jcr/2.0/javax/jcr/Node.html#getIdentifier()
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SLING-12300) Provide a way to retrieve a JCR backed resource by its node identifier
[
https://issues.apache.org/jira/browse/SLING-12300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839155#comment-17839155
]
Eric Norman commented on SLING-12300:
-
[~radu] I know how long a UUID value is, how it is formatted and what
characters are allowed in there. That is a much smaller universe then all the
possible paths that may exist.
I still having seen a good reason why this is needed.
> Provide a way to retrieve a JCR backed resource by its node identifier
> --
>
> Key: SLING-12300
> URL: https://issues.apache.org/jira/browse/SLING-12300
> Project: Sling
> Issue Type: New Feature
> Components: JCR
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: JCR Resource 3.3.0
>
>
> Since all {{javax.jcr.Nodes}} have an identifier [0], a useful feature would
> be {{Resource}} retrieval by node id, which could be its {{jcr:uuid}}
> property for referenceable nodes or the path. In systems that would like to
> use UUID addressing, this would reduce the need for executing JCR queries for
> resource retrieval and would avoid double-reads via the JCR and then Sling
> API to obtain the resource.
> In order to provide a unified behaviour, paths starting with the {{/jcr:id/}}
> prefix should use the resource retrieval by node identifier.
> [0] -
> https://javadoc.io/static/javax.jcr/jcr/2.0/javax/jcr/Node.html#getIdentifier()
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SLING-12300) Provide a way to retrieve a JCR backed resource by its node identifier
[
https://issues.apache.org/jira/browse/SLING-12300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839145#comment-17839145
]
Eric Norman commented on SLING-12300:
-
[~radu] the size of the number is irrelevant. I could get a match on the
first try if I get lucky. Basically, I'm not putting a server on the public
internet with predictable addresses. The resource path is the only address I
need.
I'm not sure this solution is necessary for general usage and you can make a
private implementation for your use case if you really need it.
> Provide a way to retrieve a JCR backed resource by its node identifier
> --
>
> Key: SLING-12300
> URL: https://issues.apache.org/jira/browse/SLING-12300
> Project: Sling
> Issue Type: New Feature
> Components: JCR
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: JCR Resource 3.3.0
>
>
> Since all {{javax.jcr.Nodes}} have an identifier [0], a useful feature would
> be {{Resource}} retrieval by node id, which could be its {{jcr:uuid}}
> property for referenceable nodes or the path. In systems that would like to
> use UUID addressing, this would reduce the need for executing JCR queries for
> resource retrieval and would avoid double-reads via the JCR and then Sling
> API to obtain the resource.
> In order to provide a unified behaviour, paths starting with the {{/jcr:id/}}
> prefix should use the resource retrieval by node identifier.
> [0] -
> https://javadoc.io/static/javax.jcr/jcr/2.0/javax/jcr/Node.html#getIdentifier()
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SLING-12300) Provide a way to retrieve a JCR backed resource by its node identifier
[
https://issues.apache.org/jira/browse/SLING-12300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839135#comment-17839135
]
Eric Norman commented on SLING-12300:
-
I think I would prefer that the uuid not be addressable so easily. That seems
to be a security hole where someone could just do a brute force attack to try
all the possible values and find paths that exist.
> Provide a way to retrieve a JCR backed resource by its node identifier
> --
>
> Key: SLING-12300
> URL: https://issues.apache.org/jira/browse/SLING-12300
> Project: Sling
> Issue Type: New Feature
> Components: JCR
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: JCR Resource 3.3.0
>
>
> Since all {{javax.jcr.Nodes}} have an identifier [0], a useful feature would
> be {{Resource}} retrieval by node id, which could be its {{jcr:uuid}}
> property for referenceable nodes or the path. In systems that would like to
> use UUID addressing, this would reduce the need for executing JCR queries for
> resource retrieval and would avoid double-reads via the JCR and then Sling
> API to obtain the resource.
> In order to provide a unified behaviour, paths starting with the {{/jcr:id/}}
> prefix should use the resource retrieval by node identifier.
> [0] -
> https://javadoc.io/static/javax.jcr/jcr/2.0/javax/jcr/Node.html#getIdentifier()
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (SLING-11906) Migrate to slf4j 2.x
[ https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman reassigned SLING-11906: --- Assignee: Eric Norman > Migrate to slf4j 2.x > > > Key: SLING-11906 > URL: https://issues.apache.org/jira/browse/SLING-11906 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: Commons Log 6.0.0 > > > Increasingly more libraries have been migrating to slf4j 2.x (for example > logback 1.3+, tika 2.5+ and jetty 10+) > To be compatible with those, the sling commons log bundle should migrate to > slf4j v2.x (and logback v1.4.x or v1.3.x?) > It looks like slf4j 2.x exports both 2.x and 1.7.36 versions of the exported > packages, so it should hopefully be compatible with existing bundles that are > importing the 1.x version of the slf4j packages. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [RESULT] [VOTE] Release Apache Sling Commons Log 5.5.0
Hi Robert. I think you may have missed the step that pushes the release to maven central for this one? The 5.5.0 version is not on maven central and the staging repository still exists. Regards, Eric On Tue, Feb 6, 2024 at 5:17 AM Robert Munteanu wrote: > Hi, > > The vote has passed with the following result: > > +1 (binding): Robert Munteanu, Stefan Seifert, Carsten Ziegeler, Joerg > Hoh, Eric Norman > +1 (non-binding): none > > I will copy this release to the Sling dist directory and > promote the artifacts to the central Maven repository. > > Regards, > Robert Munteanu > >
Re: [VOTE] Release Apache Sling Commons Log 5.5.0
+1 On Mon, Jan 29, 2024 at 4:38 AM Robert Munteanu wrote: > Hi, > > We solved 2 issues in this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12354154=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2835/ > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2835 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Regards, > Robert Munteanu >
Re: [VOTE] Release Apache Resource Resolver 1.11.6
Julian, FWIW: disagreeing is not the same thing as "ignoring". Well, you did more than just disagree. There was no followup to any of the 3 replies to explain your position. I'm not a mind reader. On Mon, Jan 22, 2024 at 1:15 AM Julian Reschke wrote: > On 20.01.2024 02:09, Eric Norman wrote: > > +0 for me. > > > > Though, I am still a little annoyed that you just ignored my review > > comments from > > > https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/109#pullrequestreview-1791514750 > > Eric, > > FWIW: disagreeing is not the same thing as "ignoring". This change was > urgent because it addresses a customer-visible defect (aliases broken > when more than >100K). What you raised is a stylistic issue which is not > specific to this PR, so it really ought to be addressed/discussed as > separate issue. > > Best regards, Julian >
Re: [VOTE] Release Apache Sling Testing JCR Mock 1.6.14, OSGi Mock 3.4.2, ResourceResolver Mock 1.4.6, Sling Mock 3.4.18
+1 On Mon, Jan 22, 2024 at 6:56 AM Stefan Seifert wrote: > Hi, > > Testing JCR Mock 1.6.14 (1 issue) > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12354068=Text=12310710 > > Testing OSGi Mock 3.4.2 (1 issue) > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353872=Text=12310710 > > Testing ResourceResolver Mock 1.4.6 (1 issue) > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353544=Text=12310710 > > Testing Sling Mock 3.4.18 (1 issue) > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12354009=Text=12310710 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2832/ > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2832 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > stefan >
Re: [VOTE] Release Apache Resource Resolver 1.11.6
+0 for me. Though, I am still a little annoyed that you just ignored my review comments from https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/109#pullrequestreview-1791514750 On Tue, Jan 16, 2024 at 10:52 PM Julian Reschke wrote: > Hi, > > We solved 6 issues in this release: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353856=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2830 > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2830 /tmp/sling-staging > > Please vote to approve this release: > >[ ] +1 Approve the release >[ ] 0 Don't care >[ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Best regards, Julian >
Re: [VOTE] Release Apache Sling Testing Clients 3.0.22
+1 On Mon, Jan 15, 2024 at 2:09 AM Andrei Dulvac wrote: > Hi, > > We solved 5 issues in this release: > https://issues.apache.org/jira/projects/SLING/versions/12353709 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2829/ > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2829 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > - Andrei >
[jira] [Closed] (SLING-12224) Remove dependency on org.apache.sling.jcr.base
[ https://issues.apache.org/jira/browse/SLING-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12224. --- > Remove dependency on org.apache.sling.jcr.base > -- > > Key: SLING-12224 > URL: https://issues.apache.org/jira/browse/SLING-12224 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Jackrabbit Access Manager 4.0.2 > > > Remove dependency on org.apache.sling.jcr.base since it is only used for > AccessControlUtil methods to access the UserManager and PrincipalManager. > Since this bundle is a jackrabbit/oak specific implementation we can use the > JackrabbitSession methods to accomplish the same without the dependency. > > This refactoring simplifies using sling mocks for tests that interact with > this code since you only need to mock the AccessControlManager itself and not > also the AccessControlUtil static methods. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[RESULT] [VOTE] Release Apache Sling JCR Jackrabbit Access Manager version 4.0.2
Hi, The vote has passed with the following result : +1 (binding): Eric Norman, Stefan Seifert, Robert Munteanu, Jörg Hoh +1 (non binding): none I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository.
Re: [VOTE] Release Apache Sling JCR Jackrabbit Access Manager version 4.0.2
+1 for me We still need two more binding vote for this one. Please review and provide a vote if you are a PMC member and have the time. Regards, Eric On Mon, Jan 8, 2024 at 4:02 PM Eric Norman wrote: > Hi, > > We solved 1 issues in this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353756=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2827/ > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2827 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. >
Re: Sling Johnzon Wrapper & Jakarta JSON
For the record, I am not saying this change is good or bad. However, no one responded to my feedback which doesn't feel like community consensus to me. No vote was taken, it was just done how Carsten wanted it to be done. Regards, Eric On Thu, Jan 11, 2024 at 6:10 AM Robert Munteanu wrote: > For the record: > > - starting with > > https://github.com/apache/sling-org-apache-sling-starter/commit/31e6d31de2ddbb740b553c9c6775e021b5b1d57b > we are using our own Johnzon wrapper, which does not need the SPIFly > mediator > - the SPIFly mediator is still present as it's needed by the Groovy > bundles > > Overall a good balance IMO, thanks Carsten for making the changes. > > Robert > > On Mon, 2023-11-20 at 15:25 -0800, Eric Norman wrote: > > Hi Carsten, > > > > For me, requiring a service loader mediator isn't a deal breaker. > > There > > are other parts of my projects that already require it to be there. > > The > > configuration setup is a one time thing and the runtime overhead > > appears to > > be insignificant. > > > > For example, > > > >1. Jetty - The "light" classifier of the > > org.apache.felix.http.jetty > >bundle requires the use of the ServiceLoader to find services > > provided by > >the various jetty* bundles > >2. SLING-11906 <https://issues.apache.org/jira/browse/SLING-11906> > > - > >SLF4j 2.x uses the ServiceLoader to locate the logging > > implementation. So > >any bundles that have migrated to slf4j 2.x (for example logback > > 1.3+, tika > >2.5+ and jetty 10+) would require a serviceloader mediator as > > well. > > > > > > Regards, > > Eric > > > > On Mon, Nov 20, 2023 at 12:57 AM Carsten Ziegeler > > > > wrote: > > > > > I think the downside of all of these solutions is that they all > > > require > > > service loader support - which drags in a lot of other stuff. > > > We should try to convince the johnzon community to remove the hard > > > requirement on serviceloader - it doesn't really make sense in this > > > case. and then we would have an apache, dependency free > > > implementation. > > > > > > To avoid all those dependencies I switched to > > > "org.glassfish:jakarta.json:2.0.1" for my projects. Its older, but > > > works > > > and does not require service loader or anything else at all. > > > > > > Regards > > > Carsten > > > > > > On 17.11.2023 20:37, Eric Norman wrote: > > > > Is the johnzon 2.x implementation better than the parsson library > > > > that we > > > > are already including in the starter? > > > > > > > > I've just been switching the geronimo-json_1.0_spec and johnzon- > > > > core > > > > dependencies to these: > > > > > > > > > > > > > > > > jakarta.json > > > > jakarta.json-api > > > > 2.1.1 > > > > provided > > > > > > > > > > > > > > Carsten Ziegeler > > > Adobe > > > cziege...@apache.org > > > > >
[VOTE] Release Apache Sling JCR Jackrabbit Access Manager version 4.0.2
Hi, We solved 1 issues in this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353756=Text Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2827/ You can use this UNIX script to download the release and verify the signatures: https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh Usage: sh check_staged_release.sh 2827 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours.
[jira] [Resolved] (SLING-12224) Remove dependency on org.apache.sling.jcr.base
[
https://issues.apache.org/jira/browse/SLING-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-12224.
-
Resolution: Fixed
Merged PR at:
[{{7c0138c}}|https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-accessmanager/commit/7c0138c957cc1be15c72f62349636b4f5ffd4142]
> Remove dependency on org.apache.sling.jcr.base
> --
>
> Key: SLING-12224
> URL: https://issues.apache.org/jira/browse/SLING-12224
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: JCR Jackrabbit Access Manager 4.0.2
>
>
> Remove dependency on org.apache.sling.jcr.base since it is only used for
> AccessControlUtil methods to access the UserManager and PrincipalManager.
> Since this bundle is a jackrabbit/oak specific implementation we can use the
> JackrabbitSession methods to accomplish the same without the dependency.
>
> This refactoring simplifies using sling mocks for tests that interact with
> this code since you only need to mock the AccessControlManager itself and not
> also the AccessControlUtil static methods.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SLING-12224) Remove dependency on org.apache.sling.jcr.base
Eric Norman created SLING-12224: --- Summary: Remove dependency on org.apache.sling.jcr.base Key: SLING-12224 URL: https://issues.apache.org/jira/browse/SLING-12224 Project: Sling Issue Type: Improvement Reporter: Eric Norman Assignee: Eric Norman Fix For: JCR Jackrabbit Access Manager 4.0.2 Remove dependency on org.apache.sling.jcr.base since it is only used for AccessControlUtil methods to access the UserManager and PrincipalManager. Since this bundle is a jackrabbit/oak specific implementation we can use the JackrabbitSession methods to accomplish the same without the dependency. This refactoring simplifies using sling mocks for tests that interact with this code since you only need to mock the AccessControlManager itself and not also the AccessControlUtil static methods. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12190) MockUser should provide more real password handling
[ https://issues.apache.org/jira/browse/SLING-12190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12190. --- > MockUser should provide more real password handling > --- > > Key: SLING-12190 > URL: https://issues.apache.org/jira/browse/SLING-12190 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: Testing JCR Mock 1.6.12 > > > When creating a new user via the MockUserManager, the supplied user password > was being ignored. > To allow more real testing around the changing the password, the MockUser > password handling should be more real. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12168) Implement MockUserManager#createSystemUser
[ https://issues.apache.org/jira/browse/SLING-12168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12168. --- > Implement MockUserManager#createSystemUser > -- > > Key: SLING-12168 > URL: https://issues.apache.org/jira/browse/SLING-12168 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: Testing JCR Mock 1.6.12 > > > Provide a basic implementation of the MockUserManager#createSystemUser method. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12195) MockUser use a property on the home node for the disabled state
[ https://issues.apache.org/jira/browse/SLING-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12195. --- > MockUser use a property on the home node for the disabled state > --- > > Key: SLING-12195 > URL: https://issues.apache.org/jira/browse/SLING-12195 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: Testing JCR Mock 1.6.12 > > > Instead of managing the disabled state as a field of MockUser, it should be > stored as a property on the user's home node. > This ensures that the disabled state remains available when a new > ResourceResolver is created via > ResourceResolverFactory#getServiceResourceResolver > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12167) MockAuthorizable setProperty(String, Value[]) should create any missing intermediate nodes
[ https://issues.apache.org/jira/browse/SLING-12167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12167. --- > MockAuthorizable setProperty(String, Value[]) should create any missing > intermediate nodes > -- > > Key: SLING-12167 > URL: https://issues.apache.org/jira/browse/SLING-12167 > Project: Sling > Issue Type: Bug > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: Testing JCR Mock 1.6.12 > > > MockAuthorizable setProperty(String, Value[]) should create any missing > intermediate nodes > If the relPath argument contains multiple segments, then any missing > intermediate nodes should be autocreated -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12166) MockUserManager getAuthorizable(String, Class) should return null if the authorizable does not exist
[ https://issues.apache.org/jira/browse/SLING-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12166. --- > MockUserManager getAuthorizable(String, Class) should return null if the > authorizable does not exist > > > Key: SLING-12166 > URL: https://issues.apache.org/jira/browse/SLING-12166 > Project: Sling > Issue Type: Bug > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: Testing JCR Mock 1.6.12 > > > MockUserManager#getAuthorizable(String, Class) should return null if the user > or group does not exist. Currently it throws a AuthorizableTypeException > instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12196) allowSelfChangePassword config key does not match
[ https://issues.apache.org/jira/browse/SLING-12196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12196. --- > allowSelfChangePassword config key does not match > - > > Key: SLING-12196 > URL: https://issues.apache.org/jira/browse/SLING-12196 > Project: Sling > Issue Type: Bug > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Jackrabbit User Manager 2.2.30 > > > The ChangeUserPasswordServlet$Config OCD defines the "Allow Self Password > Change" value that uses the "allowSelfChangePassword" key. > Unfortunately, the ChangeUserPasswordServlet#activate and > AuthorizablePrivilegesInfoImpl#bindChangeUserPassword code was using > "alwaysAllowSelfChangePassword" as the config property name which does not > match the name defined in the config definition. > > Expected: > Change the code to use the correct property name. Also, provide backward > compatibility by checking for the old name as well and log a warning to > prompt the user to update their configuration. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12185) AuthorizableResourceProvider getResource matches wrong prefix
[
https://issues.apache.org/jira/browse/SLING-12185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman closed SLING-12185.
---
> AuthorizableResourceProvider getResource matches wrong prefix
> -
>
> Key: SLING-12185
> URL: https://issues.apache.org/jira/browse/SLING-12185
> Project: Sling
> Issue Type: Bug
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: JCR Jackrabbit User Manager 2.2.30
>
>
> resourceResolver.getResource("/userManager/user/group1") returns a resource
> object when it should return null because the path of the group resource is
> actually "/userManager/group/group1"
>
> Expected:
> The AuthorizableResourceProvider needs to check the type of the found
> Authorizable to ensure that the object type matches the expected resource
> path prefix before using it to return an AuthorizableResource.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SLING-12203) Remove dependency on org.apache.sling.jcr.base
[ https://issues.apache.org/jira/browse/SLING-12203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12203. --- > Remove dependency on org.apache.sling.jcr.base > -- > > Key: SLING-12203 > URL: https://issues.apache.org/jira/browse/SLING-12203 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Jackrabbit User Manager 2.2.30 > > > Remove dependency on org.apache.sling.jcr.base since it is only used for > AccessControlUtil methods to access the UserManager and PrincipalManager. > Since this bundle is a jackrabbit/oak specific implementation we can use the > JackrabbitSession methods to accomplish the same without the dependency. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12202) add AuthorizablePrivilegesInfo#canChangePasswordWithoutOldPassword
[ https://issues.apache.org/jira/browse/SLING-12202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12202. --- > add AuthorizablePrivilegesInfo#canChangePasswordWithoutOldPassword > -- > > Key: SLING-12202 > URL: https://issues.apache.org/jira/browse/SLING-12202 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Jackrabbit User Manager 2.2.30 > > > The AuthorizablePrivilegesInfo should have a > canChangePasswordWithoutOldPassword method that can be called to tell if the > current user can change the password of another user without knowing the > original password of that user. This currently means the current user must > the be the admin user or a member of the configured UserAdmin group. > This would be a convenience so that "change password" UI can more easily > determine the appropriate fields to render on screen without having to > duplicate logic from the ChangeUserPasswordServlet. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[RESULT] [VOTE] Release Apache Sling JCR Jackrabbit User Manager version 2.2.30
Hi, The vote has passed with the following result : +1 (binding): Stefan Seifert, Robert Munteanu, Eric Norman +1 (non binding): none I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository.
Re: [VOTE] Release Apache Sling JCR Jackrabbit User Manager version 2.2.30
+1 On Mon, Dec 18, 2023 at 6:58 PM Eric Norman wrote: > Hi, > > We solved 4 issues in this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353755=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2825/ > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2825 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. >
[RESULT] [VOTE] Release Apache Sling Testing JCR Mock version 1.6.12
Hi, The vote has passed with the following result : +1 (binding): Stefan Seifert, Robert Munteanu, Eric Norman +1 (non binding): none I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository.
Re: [VOTE] Release Apache Sling Testing JCR Mock version 1.6.12
+1 On Mon, Dec 18, 2023 at 11:50 AM Eric Norman wrote: > Hi, > > We solved 7 issues in this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353249=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2824/ > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2824 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. >
[VOTE] Release Apache Sling JCR Jackrabbit User Manager version 2.2.30
Hi, We solved 4 issues in this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353755=Text Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2825/ You can use this UNIX script to download the release and verify the signatures: https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh Usage: sh check_staged_release.sh 2825 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours.
[jira] [Resolved] (SLING-12203) Remove dependency on org.apache.sling.jcr.base
[
https://issues.apache.org/jira/browse/SLING-12203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-12203.
-
Resolution: Fixed
Merged PR at:
[{{e92e8a8}}|https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-usermanager/commit/e92e8a8d89fafbd1f873c32b4851bf878a3457d3]
> Remove dependency on org.apache.sling.jcr.base
> --
>
> Key: SLING-12203
> URL: https://issues.apache.org/jira/browse/SLING-12203
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: JCR Jackrabbit User Manager 2.2.30
>
>
> Remove dependency on org.apache.sling.jcr.base since it is only used for
> AccessControlUtil methods to access the UserManager and PrincipalManager.
> Since this bundle is a jackrabbit/oak specific implementation we can use the
> JackrabbitSession methods to accomplish the same without the dependency.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (SLING-12202) add AuthorizablePrivilegesInfo#canChangePasswordWithoutOldPassword
[
https://issues.apache.org/jira/browse/SLING-12202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-12202.
-
Resolution: Fixed
Merged PR at:
[{{abea574}}|https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-usermanager/commit/abea5742f5bd668685a0407f0ff7de686d6a733e]
> add AuthorizablePrivilegesInfo#canChangePasswordWithoutOldPassword
> --
>
> Key: SLING-12202
> URL: https://issues.apache.org/jira/browse/SLING-12202
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: JCR Jackrabbit User Manager 2.2.30
>
>
> The AuthorizablePrivilegesInfo should have a
> canChangePasswordWithoutOldPassword method that can be called to tell if the
> current user can change the password of another user without knowing the
> original password of that user. This currently means the current user must
> the be the admin user or a member of the configured UserAdmin group.
> This would be a convenience so that "change password" UI can more easily
> determine the appropriate fields to render on screen without having to
> duplicate logic from the ChangeUserPasswordServlet.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[VOTE] Release Apache Sling Testing JCR Mock version 1.6.12
Hi, We solved 7 issues in this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353249=Text Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2824/ You can use this UNIX script to download the release and verify the signatures: https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh Usage: sh check_staged_release.sh 2824 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours.
[jira] [Created] (SLING-12203) Remove dependency on org.apache.sling.jcr.base
Eric Norman created SLING-12203: --- Summary: Remove dependency on org.apache.sling.jcr.base Key: SLING-12203 URL: https://issues.apache.org/jira/browse/SLING-12203 Project: Sling Issue Type: Improvement Reporter: Eric Norman Assignee: Eric Norman Fix For: JCR Jackrabbit User Manager 2.2.30 Remove dependency on org.apache.sling.jcr.base since it is only used for AccessControlUtil methods to access the UserManager and PrincipalManager. Since this bundle is a jackrabbit/oak specific implementation we can use the JackrabbitSession methods to accomplish the same without the dependency. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12202) add AuthorizablePrivilegesInfo#canChangePasswordWithoutOldPassword
Eric Norman created SLING-12202: --- Summary: add AuthorizablePrivilegesInfo#canChangePasswordWithoutOldPassword Key: SLING-12202 URL: https://issues.apache.org/jira/browse/SLING-12202 Project: Sling Issue Type: Improvement Reporter: Eric Norman Assignee: Eric Norman Fix For: JCR Jackrabbit User Manager 2.2.30 The AuthorizablePrivilegesInfo should have a canChangePasswordWithoutOldPassword method that can be called to tell if the current user can change the password of another user without knowing the original password of that user. This currently means the current user must the be the admin user or a member of the configured UserAdmin group. This would be a convenience so that "change password" UI can more easily determine the appropriate fields to render on screen without having to duplicate logic from the ChangeUserPasswordServlet. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-12196) allowSelfChangePassword config key does not match
[
https://issues.apache.org/jira/browse/SLING-12196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-12196.
-
Resolution: Fixed
Merged PR at:
[{{84c75c5}}|https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-usermanager/commit/84c75c5f242db21d199ca472b65929f3f8d85bc3]
> allowSelfChangePassword config key does not match
> -
>
> Key: SLING-12196
> URL: https://issues.apache.org/jira/browse/SLING-12196
> Project: Sling
> Issue Type: Bug
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: JCR Jackrabbit User Manager 2.2.30
>
>
> The ChangeUserPasswordServlet$Config OCD defines the "Allow Self Password
> Change" value that uses the "allowSelfChangePassword" key.
> Unfortunately, the ChangeUserPasswordServlet#activate and
> AuthorizablePrivilegesInfoImpl#bindChangeUserPassword code was using
> "alwaysAllowSelfChangePassword" as the config property name which does not
> match the name defined in the config definition.
>
> Expected:
> Change the code to use the correct property name. Also, provide backward
> compatibility by checking for the old name as well and log a warning to
> prompt the user to update their configuration.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [VOTE] Release Apache Sling Engine 2.15.10
0 for me. I would probably prefer that the SLING-12124 changes not be reverted as leaving the old behavior could be somewhat of a security risk. For example, I could put enough extra dots in the url to push some details of the address off the right edge of the browser's address bar in order to obscure information from the user in order to trick them into doing something they wouldn't otherwise do if the canonical address was fully visible. Perhaps there is a convenient way that the SLING-12124 behavior could be made optional via some configuration flag? Or at least some feedback somewhere to nudge the end user into using a well formed address? Regards, -Eric On Fri, Dec 15, 2023 at 3:56 AM Carsten Ziegeler wrote: > Hi, > > We solved 1 issue in this release > https://issues.apache.org/jira/browse/SLING-12201 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2823/ > > You can use this UNIX script to download the release and verify the > signatures: > > https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD > > Usage: > sh check_staged_release.sh 2823 /tmp/sling-staging > > Please vote to approve this release: > >[ ] +1 Approve the release >[ ] 0 Don't care >[ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Regards > Carsten > -- > Carsten Ziegeler > Adobe > cziege...@apache.org >
[jira] [Resolved] (SLING-12195) MockUser use a property on the home node for the disabled state
[
https://issues.apache.org/jira/browse/SLING-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-12195.
-
Resolution: Fixed
Merged PR at:
[{{3b2a6bf}}|https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/commit/3b2a6bf5131cd82bab50939ed7f2e79aeb0bf08a]
> MockUser use a property on the home node for the disabled state
> ---
>
> Key: SLING-12195
> URL: https://issues.apache.org/jira/browse/SLING-12195
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: Testing JCR Mock 1.6.12
>
>
> Instead of managing the disabled state as a field of MockUser, it should be
> stored as a property on the user's home node.
> This ensures that the disabled state remains available when a new
> ResourceResolver is created via
> ResourceResolverFactory#getServiceResourceResolver
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [VOTE] Release Apache Sling Testing Sling Mock 3.4.16
+1 On Thu, Dec 7, 2023 at 8:59 AM Stefan Seifert wrote: > Hi, > > We solved 2 issues in this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353706=Text=12310710 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2820/ > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2820 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > stefan >
[jira] [Created] (SLING-12196) allowSelfChangePassword config key does not match
Eric Norman created SLING-12196: --- Summary: allowSelfChangePassword config key does not match Key: SLING-12196 URL: https://issues.apache.org/jira/browse/SLING-12196 Project: Sling Issue Type: Bug Reporter: Eric Norman Assignee: Eric Norman Fix For: JCR Jackrabbit User Manager 2.2.30 The ChangeUserPasswordServlet$Config OCD defines the "Allow Self Password Change" value that uses the "allowSelfChangePassword" key. Unfortunately, the ChangeUserPasswordServlet#activate and AuthorizablePrivilegesInfoImpl#bindChangeUserPassword code was using "alwaysAllowSelfChangePassword" as the config property name which does not match the name defined in the config definition. Expected: Change the code to use the correct property name. Also, provide backward compatibility by checking for the old name as well and log a warning to prompt the user to update their configuration. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12195) MockUser use a property on the home node for the disabled state
[ https://issues.apache.org/jira/browse/SLING-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman updated SLING-12195: Description: Instead of managing the disabled state as a field of MockUser, it should be stored as a property on the user's home node. This ensures that the disabled state remains available when a new ResourceResolver is created via ResourceResolverFactory#getServiceResourceResolver was: Instead of managing the disabled state as a field of MockUser, it should stored as a property on the user's home node. This ensures that the disabled state remains available when a new ResourceResolver is created via ResourceResolverFactory#getServiceResourceResolver > MockUser use a property on the home node for the disabled state > --- > > Key: SLING-12195 > URL: https://issues.apache.org/jira/browse/SLING-12195 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: Testing JCR Mock 1.6.12 > > > Instead of managing the disabled state as a field of MockUser, it should be > stored as a property on the user's home node. > This ensures that the disabled state remains available when a new > ResourceResolver is created via > ResourceResolverFactory#getServiceResourceResolver > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12195) MockUser use a property on the home node for the disabled state
Eric Norman created SLING-12195: --- Summary: MockUser use a property on the home node for the disabled state Key: SLING-12195 URL: https://issues.apache.org/jira/browse/SLING-12195 Project: Sling Issue Type: Improvement Reporter: Eric Norman Assignee: Eric Norman Fix For: Testing JCR Mock 1.6.12 Instead of managing the disabled state as a field of MockUser, it should stored as a property on the user's home node. This ensures that the disabled state remains available when a new ResourceResolver is created via ResourceResolverFactory#getServiceResourceResolver -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-12190) MockUser should provide more real password handling
[
https://issues.apache.org/jira/browse/SLING-12190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-12190.
-
Resolution: Fixed
Merged PR at:
[{{a27a118}}|https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/commit/a27a11874d605793579a2f951a2097a5829d0073]
> MockUser should provide more real password handling
> ---
>
> Key: SLING-12190
> URL: https://issues.apache.org/jira/browse/SLING-12190
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: Testing JCR Mock 1.6.12
>
>
> When creating a new user via the MockUserManager, the supplied user password
> was being ignored.
> To allow more real testing around the changing the password, the MockUser
> password handling should be more real.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SLING-12190) MockUser should provide more real password handling
Eric Norman created SLING-12190: --- Summary: MockUser should provide more real password handling Key: SLING-12190 URL: https://issues.apache.org/jira/browse/SLING-12190 Project: Sling Issue Type: Improvement Reporter: Eric Norman Assignee: Eric Norman Fix For: Testing JCR Mock 1.6.12 When creating a new user via the MockUserManager, the supplied user password was being ignored. To allow more real testing around the changing the password, the MockUser password handling should be more real. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-12168) Implement MockUserManager#createSystemUser
[
https://issues.apache.org/jira/browse/SLING-12168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-12168.
-
Resolution: Fixed
Merged PR at:
[{{7929b38}}|https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/commit/7929b388537494b0d77fd6a12ef4352e30a75784]
> Implement MockUserManager#createSystemUser
> --
>
> Key: SLING-12168
> URL: https://issues.apache.org/jira/browse/SLING-12168
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: Testing JCR Mock 1.6.12
>
>
> Provide a basic implementation of the MockUserManager#createSystemUser method.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (SLING-12185) AuthorizableResourceProvider getResource matches wrong prefix
[
https://issues.apache.org/jira/browse/SLING-12185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-12185.
-
Resolution: Fixed
Merged PR at:
[{{bfa57e7}}|https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-usermanager/commit/bfa57e790ccd2c47440223e6482b5da46090f148]
> AuthorizableResourceProvider getResource matches wrong prefix
> -
>
> Key: SLING-12185
> URL: https://issues.apache.org/jira/browse/SLING-12185
> Project: Sling
> Issue Type: Bug
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: JCR Jackrabbit User Manager 2.2.30
>
>
> resourceResolver.getResource("/userManager/user/group1") returns a resource
> object when it should return null because the path of the group resource is
> actually "/userManager/group/group1"
>
> Expected:
> The AuthorizableResourceProvider needs to check the type of the found
> Authorizable to ensure that the object type matches the expected resource
> path prefix before using it to return an AuthorizableResource.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SLING-12185) AuthorizableResourceProvider getResource matches wrong prefix
Eric Norman created SLING-12185:
---
Summary: AuthorizableResourceProvider getResource matches wrong
prefix
Key: SLING-12185
URL: https://issues.apache.org/jira/browse/SLING-12185
Project: Sling
Issue Type: Bug
Reporter: Eric Norman
Assignee: Eric Norman
Fix For: JCR Jackrabbit User Manager 2.2.30
resourceResolver.getResource("/userManager/user/group1") returns a resource
object when it should return null because the path of the group resource is
actually "/userManager/group/group1"
Expected:
The AuthorizableResourceProvider needs to check the type of the found
Authorizable to ensure that the object type matches the expected resource path
prefix before using it to return an AuthorizableResource.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-12168) Implement MockUserManager#createSystemUser
[ https://issues.apache.org/jira/browse/SLING-12168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman updated SLING-12168: Description: Provide a basic implementation of the MockUserManager#createSystemUser method. (was: Provide a basic Implement of the MockUserManager#createSystemUser method.) > Implement MockUserManager#createSystemUser > -- > > Key: SLING-12168 > URL: https://issues.apache.org/jira/browse/SLING-12168 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: Testing JCR Mock 1.6.12 > > > Provide a basic implementation of the MockUserManager#createSystemUser method. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-12167) MockAuthorizable setProperty(String, Value[]) should create any missing intermediate nodes
[
https://issues.apache.org/jira/browse/SLING-12167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-12167.
-
Resolution: Fixed
Merged PR at:
[{{f9c25bc}}|https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/commit/f9c25bcb718f6f83e52d683757c57c24d132cdbd]
> MockAuthorizable setProperty(String, Value[]) should create any missing
> intermediate nodes
> --
>
> Key: SLING-12167
> URL: https://issues.apache.org/jira/browse/SLING-12167
> Project: Sling
> Issue Type: Bug
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: Testing JCR Mock 1.6.12
>
>
> MockAuthorizable setProperty(String, Value[]) should create any missing
> intermediate nodes
> If the relPath argument contains multiple segments, then any missing
> intermediate nodes should be autocreated
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (SLING-12166) MockUserManager getAuthorizable(String, Class) should return null if the authorizable does not exist
[
https://issues.apache.org/jira/browse/SLING-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-12166.
-
Resolution: Fixed
Merged PR at:
[{{34c4370}}|https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/commit/34c437066edd7fb74ee4ab8d68c425bbd315e8a5]
> MockUserManager getAuthorizable(String, Class) should return null if the
> authorizable does not exist
>
>
> Key: SLING-12166
> URL: https://issues.apache.org/jira/browse/SLING-12166
> Project: Sling
> Issue Type: Bug
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: Testing JCR Mock 1.6.12
>
>
> MockUserManager#getAuthorizable(String, Class) should return null if the user
> or group does not exist. Currently it throws a AuthorizableTypeException
> instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SLING-12168) Implement MockUserManager#createSystemUser
Eric Norman created SLING-12168: --- Summary: Implement MockUserManager#createSystemUser Key: SLING-12168 URL: https://issues.apache.org/jira/browse/SLING-12168 Project: Sling Issue Type: Improvement Reporter: Eric Norman Assignee: Eric Norman Fix For: Testing JCR Mock 1.6.12 Provide a basic Implement of the MockUserManager#createSystemUser method. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12167) MockAuthorizable setProperty(String, Value[]) should create any missing intermediate nodes
Eric Norman created SLING-12167: --- Summary: MockAuthorizable setProperty(String, Value[]) should create any missing intermediate nodes Key: SLING-12167 URL: https://issues.apache.org/jira/browse/SLING-12167 Project: Sling Issue Type: Bug Reporter: Eric Norman Assignee: Eric Norman Fix For: Testing JCR Mock 1.6.12 MockAuthorizable setProperty(String, Value[]) should create any missing intermediate nodes If the relPath argument contains multiple segments, then any missing intermediate nodes should be autocreated -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12166) MockUserManager getAuthorizable(String, Class) should return null if the authorizable does not exist
Eric Norman created SLING-12166: --- Summary: MockUserManager getAuthorizable(String, Class) should return null if the authorizable does not exist Key: SLING-12166 URL: https://issues.apache.org/jira/browse/SLING-12166 Project: Sling Issue Type: Bug Reporter: Eric Norman Assignee: Eric Norman Fix For: Testing JCR Mock 1.6.12 MockUserManager#getAuthorizable(String, Class) should return null if the user or group does not exist. Currently it throws a AuthorizableTypeException instead. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Sling Johnzon Wrapper & Jakarta JSON
Hi Carsten, For me, requiring a service loader mediator isn't a deal breaker. There are other parts of my projects that already require it to be there. The configuration setup is a one time thing and the runtime overhead appears to be insignificant. For example, 1. Jetty - The "light" classifier of the org.apache.felix.http.jetty bundle requires the use of the ServiceLoader to find services provided by the various jetty* bundles 2. SLING-11906 <https://issues.apache.org/jira/browse/SLING-11906> - SLF4j 2.x uses the ServiceLoader to locate the logging implementation. So any bundles that have migrated to slf4j 2.x (for example logback 1.3+, tika 2.5+ and jetty 10+) would require a serviceloader mediator as well. Regards, Eric On Mon, Nov 20, 2023 at 12:57 AM Carsten Ziegeler wrote: > I think the downside of all of these solutions is that they all require > service loader support - which drags in a lot of other stuff. > We should try to convince the johnzon community to remove the hard > requirement on serviceloader - it doesn't really make sense in this > case. and then we would have an apache, dependency free implementation. > > To avoid all those dependencies I switched to > "org.glassfish:jakarta.json:2.0.1" for my projects. Its older, but works > and does not require service loader or anything else at all. > > Regards > Carsten > > On 17.11.2023 20:37, Eric Norman wrote: > > Is the johnzon 2.x implementation better than the parsson library that we > > are already including in the starter? > > > > I've just been switching the geronimo-json_1.0_spec and johnzon-core > > dependencies to these: > > > > > > > > jakarta.json > > jakarta.json-api > > 2.1.1 > > provided > > > > > > > > > > org.eclipse.parsson > > parsson > > 1.1.1 > > test > > > > > > Regards, > > -Eric > > > > On Fri, Nov 17, 2023 at 3:03 AM Stefan Seifert > > wrote: > > > >> in context of SLING-12058 we are migrating lots of modules from > javax.json > >> to jakarta.json. this works fine for modules using javax.json directly. > >> > >> however, we have a few modules which are using johnzon, which uses > >> javax.json internally. since version johnzon 1.2.5 (we are using johnzon > >> 1.2.21 in latest wrapper bundle) johnzon ships an additional artifact > with > >> classifier "jakarta", which uses jakarta.json internally. both artifacts > >> with and without "jakarta" are identical, except the internal usage of > the > >> package name. our wrapper bundle contains the version using javax.json. > >> > >> for non-bundles like maven plugins we can just switch to the artifact > with > >> "jakarta". but this will not work for our bundles. we cannot ship both > >> artifacts with and without "jakarta" classifier as wrapper bundles and > >> export them both in OSGi with the same version number. i've found at > least > >> one bundle where this is already used (but not released) [1]. it > stumbled > >> about this in PR [2]. the bundles might work anyway as the bundle > compiled > >> against the johnzon "jakarta" affect should also work with the > javax.json > >> version at runtime, but this feels like a slippery slope. > >> > >> according to [3] johnzon is using a different way starting from version > >> 2.0 (which seems to be released a few days ago, although the homepage is > >> not updated yet): in version 2.0 johnzon uses only jakarta.json. > >> > >> so it think the correct way is to create and deploy an additional > wrapper > >> bundle for johnzon 2.0, which we can deploy side-by-side with the old > >> wrapper bundle with 1.x. i assume we have to support both of them for > quite > >> a time, as there is a lot of code out there using johnzon 1.x. > >> > >> WDYT? > >> > >> stefan > >> > >> [1] > >> > https://github.com/apache/sling-org-apache-sling-installer-factory-feature/blob/867bd44f0991cedd130314d833c9aac29ae3f36c/pom.xml#L134-L140 > >> [2] https://github.com/apache/sling-org-apache-sling-fsresource/pull/2 > >> [3] https://johnzon.apache.org/download.html > >> > > > > -- > Carsten Ziegeler > Adobe > cziege...@apache.org >
Re: Sling Johnzon Wrapper & Jakarta JSON
Is the johnzon 2.x implementation better than the parsson library that we are already including in the starter? I've just been switching the geronimo-json_1.0_spec and johnzon-core dependencies to these: jakarta.json jakarta.json-api 2.1.1 provided org.eclipse.parsson parsson 1.1.1 test Regards, -Eric On Fri, Nov 17, 2023 at 3:03 AM Stefan Seifert wrote: > in context of SLING-12058 we are migrating lots of modules from javax.json > to jakarta.json. this works fine for modules using javax.json directly. > > however, we have a few modules which are using johnzon, which uses > javax.json internally. since version johnzon 1.2.5 (we are using johnzon > 1.2.21 in latest wrapper bundle) johnzon ships an additional artifact with > classifier "jakarta", which uses jakarta.json internally. both artifacts > with and without "jakarta" are identical, except the internal usage of the > package name. our wrapper bundle contains the version using javax.json. > > for non-bundles like maven plugins we can just switch to the artifact with > "jakarta". but this will not work for our bundles. we cannot ship both > artifacts with and without "jakarta" classifier as wrapper bundles and > export them both in OSGi with the same version number. i've found at least > one bundle where this is already used (but not released) [1]. it stumbled > about this in PR [2]. the bundles might work anyway as the bundle compiled > against the johnzon "jakarta" affect should also work with the javax.json > version at runtime, but this feels like a slippery slope. > > according to [3] johnzon is using a different way starting from version > 2.0 (which seems to be released a few days ago, although the homepage is > not updated yet): in version 2.0 johnzon uses only jakarta.json. > > so it think the correct way is to create and deploy an additional wrapper > bundle for johnzon 2.0, which we can deploy side-by-side with the old > wrapper bundle with 1.x. i assume we have to support both of them for quite > a time, as there is a lot of code out there using johnzon 1.x. > > WDYT? > > stefan > > [1] > https://github.com/apache/sling-org-apache-sling-installer-factory-feature/blob/867bd44f0991cedd130314d833c9aac29ae3f36c/pom.xml#L134-L140 > [2] https://github.com/apache/sling-org-apache-sling-fsresource/pull/2 > [3] https://johnzon.apache.org/download.html >
Re: [VOTE] Release Apache Sling XSS Protection API 2.4.0
+1 LGTM On Fri, Nov 10, 2023 at 8:22 AM Robert Munteanu wrote: > Hi, > > We solved 8 issues in this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353773=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2804/ > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2804 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Regards, > Robert Munteanu >
Re: [VOTE] Release Apache Sling XSS Protection API 2.3.10
-1 for me. This version doesn't appear to resolve when I plug it into the starter project. Were there additional new dependencies required to use it? It reports the following errors from the feature analyzer: [ERROR] [bundle-packages] org.apache.sling:org.apache.sling.xss:2.3.10: Bundle is importing packages [javax.annotation.meta, android.os] with start order 20 but no bundle is exporting these for that start order. [ERROR] Analyser detected errors on feature 'org.apache.sling:org.apache.sling.starter:slingosgifeature:oak_tar:13-SNAPSHOT'. See log output for error messages. On Thu, Oct 26, 2023 at 9:45 AM Robert Munteanu wrote: > Hi, > > We solved 6 issues in this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12353392=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2799/ > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2799 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Regards, > Robert Munteanu >
Re: svn commit: r64512 - in /release/sling: ./ checkout/ checkout/.git/ checkout/.git/hooks/ checkout/.git/info/ checkout/.git/logs/ checkout/.git/objects/ checkout/.git/objects/35/ checkout/.git/obje
Hi Andrei, Since there was no response to this, I went ahead and cleaned this up for you with these 2 revisions: r64807 | enorman | 2023-10-24 14:43:41 -0700 (Tue, 24 Oct 2023) | 1 line redo release of org.apache.sling.testing.clients-3.0.20 r64806 | enorman | 2023-10-24 14:36:08 -0700 (Tue, 24 Oct 2023) | 1 line revert revision 64512 On Fri, Oct 13, 2023 at 10:23 AM Eric Norman wrote: > Hi Andrei, > > I think you are going to want to rollback this revision from svn and try > again. > > Revision 64512 appears to contain some (but not all) of the > org.apache.sling.testing.clients-3.0.20 release binaries but also includes > a bunch of other stuff that doesn't belong there. > > Regards, > Eric > > On Fri, Oct 13, 2023 at 3:00 AM wrote: > >> Author: dulvac >> Date: Fri Oct 13 10:00:09 2023 >> New Revision: 64512 >> >> Log: >> Release org.apache.sling.testing.clients-3.0.20 >> >> >> [This commit notification would consist of 63 parts, >> which exceeds the limit of 50 ones, so it was shortened to the summary.] >> >
[jira] [Closed] (SLING-11664) the starter acl/ace pages have visible licence text at the top of the page
[ https://issues.apache.org/jira/browse/SLING-11664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-11664. --- > the starter acl/ace pages have visible licence text at the top of the page > -- > > Key: SLING-11664 > URL: https://issues.apache.org/jira/browse/SLING-11664 > Project: Sling > Issue Type: Bug > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Minor > Fix For: Starter Content 1.0.14 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The > [acl.html.esp|https://github.com/apache/sling-org-apache-sling-starter-content/blob/master/src/main/resources/initial-content/apps/sling/servlet/default/acl.html.esp] > and > [ace.html.esp|https://github.com/apache/sling-org-apache-sling-starter-content/blob/master/src/main/resources/initial-content/apps/sling/servlet/default/ace.html.esp] > scripts are using the wrong style of comments around the license text which > causes the licence text to be visible at the top of the page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12112) Update to Sling Bundle Parent 52
[ https://issues.apache.org/jira/browse/SLING-12112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12112. --- > Update to Sling Bundle Parent 52 > > > Key: SLING-12112 > URL: https://issues.apache.org/jira/browse/SLING-12112 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: Starter Content 1.0.14 > > > Update to Sling Bundle Parent 52 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11674) update the acl/ace pages for new SLING-11243 features
[ https://issues.apache.org/jira/browse/SLING-11674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-11674. --- > update the acl/ace pages for new SLING-11243 features > - > > Key: SLING-11674 > URL: https://issues.apache.org/jira/browse/SLING-11674 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: Starter Content 1.0.14 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > SLING-11243 added features to allow modifying an ace with more specific > restriction details > The existing acl/ace sample pages in the starter content should be updated to > demonstrate these enhancements. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12082) Migrate org.apache.sling.starter.content to jakarta.json
[ https://issues.apache.org/jira/browse/SLING-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12082. --- > Migrate org.apache.sling.starter.content to jakarta.json > > > Key: SLING-12082 > URL: https://issues.apache.org/jira/browse/SLING-12082 > Project: Sling > Issue Type: Sub-task > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: Starter Content 1.0.14 > > > After SLING-12081, then related changes are required to > org.apache.sling.starter.content to compensate. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12008) Update to Sling Bundle Parent 52
[ https://issues.apache.org/jira/browse/SLING-12008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12008. --- > Update to Sling Bundle Parent 52 > > > Key: SLING-12008 > URL: https://issues.apache.org/jira/browse/SLING-12008 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Jackrabbit Access Manager 4.0.0 > > > Update to Sling Bundle Parent 52 > Also replace the usages of dependencies that are not in the banned set. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12022) Fix test compatibility with java 17
[ https://issues.apache.org/jira/browse/SLING-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12022. --- > Fix test compatibility with java 17 > --- > > Key: SLING-12022 > URL: https://issues.apache.org/jira/browse/SLING-12022 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Jackrabbit Access Manager 4.0.0 > > > Some of the tests are failing when building with java 17. Seems to need a > bump of some dependencies to later versions and possibly other refactoring. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12081) Migrate org.apache.sling:org.apache.sling.jcr.jackrabbit.accessmanager to jakarta.json
[ https://issues.apache.org/jira/browse/SLING-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12081. --- > Migrate org.apache.sling:org.apache.sling.jcr.jackrabbit.accessmanager to > jakarta.json > -- > > Key: SLING-12081 > URL: https://issues.apache.org/jira/browse/SLING-12081 > Project: Sling > Issue Type: Sub-task > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Jackrabbit Access Manager 4.0.0 > > > Migrate org.apache.sling:org.apache.sling.jcr.jackrabbit.accessmanager to > jakarta.json > Also, the bundle version will need to be bumped to 4.x since several public > APIs have changes for this -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12105) Bump dependencies to the earliest versions without known vulnerabilities
[ https://issues.apache.org/jira/browse/SLING-12105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12105. --- > Bump dependencies to the earliest versions without known vulnerabilities > > > Key: SLING-12105 > URL: https://issues.apache.org/jira/browse/SLING-12105 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Jackrabbit Access Manager 4.0.0 > > > Mostly to keep tooling from flagging these as "vulnerabilities from > dependencies" > # bump org.apache.sling.api to 2.25.4 > # bump org.apache.sling.jcr.base to 3.1.12 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12106) Bump dependencies to the earliest versions without known vulnerabilities
[ https://issues.apache.org/jira/browse/SLING-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12106. --- > Bump dependencies to the earliest versions without known vulnerabilities > > > Key: SLING-12106 > URL: https://issues.apache.org/jira/browse/SLING-12106 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Jackrabbit User Manager 2.2.28 > > > Mostly to keep tooling from flagging these as "vulnerabilities from > dependencies" > # bump org.apache.sling.servlets.post to 2.3.22 > # bump org.apache.sling.jcr.base to 3.1.12 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12083) Migrate org.apache.sling.jcr.jackrabbit.usermanager to jakarta.json
[ https://issues.apache.org/jira/browse/SLING-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12083. --- > Migrate org.apache.sling.jcr.jackrabbit.usermanager to jakarta.json > --- > > Key: SLING-12083 > URL: https://issues.apache.org/jira/browse/SLING-12083 > Project: Sling > Issue Type: Sub-task > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Jackrabbit User Manager 2.2.28 > > > Migrate org.apache.sling.jcr.jackrabbit.usermanager to jakarta.json > The impact to this one appears to be limited to just the test code -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12007) Update to Sling Bundle Parent 52
[ https://issues.apache.org/jira/browse/SLING-12007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12007. --- > Update to Sling Bundle Parent 52 > > > Key: SLING-12007 > URL: https://issues.apache.org/jira/browse/SLING-12007 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Jackrabbit User Manager 2.2.28 > > > Update to Sling Bundle Parent 52 > Also replace the usages of dependencies that are not in the banned set. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12023) Fix test compatibility with java 17
[ https://issues.apache.org/jira/browse/SLING-12023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12023. --- > Fix test compatibility with java 17 > --- > > Key: SLING-12023 > URL: https://issues.apache.org/jira/browse/SLING-12023 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Jackrabbit User Manager 2.2.28 > > > Some of the tests are failing when building with java 17. Seems to need a > bump of some dependencies to later versions and possibly other refactoring. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[RESULT] [VOTE] Release Apache Sling JCR Jackrabbit Access Manager 4.0.0, JCR Jackrabbit User Manager 2.2.28, Starter Content 1.0.14
Hi, The vote has passed with the following result : +1 (binding): Daniel Klco, Stefan Seifert, Eric Norman +1 (non binding): none I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository.
Re: [VOTE] Release Apache Sling JCR Jackrabbit Access Manager 4.0.0, JCR Jackrabbit User Manager 2.2.28, Starter Content 1.0.14
+1 On Thu, Oct 19, 2023 at 5:55 PM Eric Norman wrote: > Hi, > > We solved 4 issues in the JCR Jackrabbit Access Manager release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12352554=Text > > We solved 4 issues in the JCR Jackrabbit User Manager release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12352227=Text > > We solved 4 issues in the Starter Content release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12351413=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2797/ > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2797 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. >
Re: [VOTE] Release Apache Sling Thumbnails version 1.0.2
+1 On Thu, Oct 19, 2023 at 7:22 PM Daniel Klco wrote: > Hi, > > We solved 3 issues in this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12350567=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2798/ > > You can use this UNIX script to download the release and verify the > signatures: > > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2798 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. >
[VOTE] Release Apache Sling JCR Jackrabbit Access Manager 4.0.0, JCR Jackrabbit User Manager 2.2.28, Starter Content 1.0.14
Hi, We solved 4 issues in the JCR Jackrabbit Access Manager release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12352554=Text We solved 4 issues in the JCR Jackrabbit User Manager release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12352227=Text We solved 4 issues in the Starter Content release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12351413=Text Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2797/ You can use this UNIX script to download the release and verify the signatures: https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh Usage: sh check_staged_release.sh 2797 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours.
[jira] [Resolved] (SLING-12112) Update to Sling Bundle Parent 52
[
https://issues.apache.org/jira/browse/SLING-12112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-12112.
-
Resolution: Fixed
Fixed at:
[{{a95c935}}|https://github.com/apache/sling-org-apache-sling-starter-content/commit/a95c935cce81e30a62f308c705fe43803fa7f6f5]
> Update to Sling Bundle Parent 52
>
>
> Key: SLING-12112
> URL: https://issues.apache.org/jira/browse/SLING-12112
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: Starter Content 1.0.14
>
>
> Update to Sling Bundle Parent 52
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (SLING-12082) Migrate org.apache.sling.starter.content to jakarta.json
[
https://issues.apache.org/jira/browse/SLING-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-12082.
-
Resolution: Fixed
Merged PR at:
[{{a95c935}}|https://github.com/apache/sling-org-apache-sling-starter-content/commit/a95c935cce81e30a62f308c705fe43803fa7f6f5]
> Migrate org.apache.sling.starter.content to jakarta.json
>
>
> Key: SLING-12082
> URL: https://issues.apache.org/jira/browse/SLING-12082
> Project: Sling
> Issue Type: Sub-task
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: Starter Content 1.0.14
>
>
> After SLING-12081, then related changes are required to
> org.apache.sling.starter.content to compensate.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-11184) Dynamically calculate the javadoc version to link to
[ https://issues.apache.org/jira/browse/SLING-11184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman updated SLING-11184: Fix Version/s: Starter Content 1.0.16 (was: Starter Content 1.0.14) > Dynamically calculate the javadoc version to link to > > > Key: SLING-11184 > URL: https://issues.apache.org/jira/browse/SLING-11184 > Project: Sling > Issue Type: New Feature > Components: Starter >Reporter: Robert Munteanu >Priority: Major > Fix For: Starter Content 1.0.16 > > > The Starter Content link to the latest released JavaDoc present on the Sling > Site. This means that for each starter release we need to update the link and > release the module. Instead, we should dynamically obtain it from the running > Starter and use it in the links. > The release version should be inferred from the pom.xml version of the > Starter module and later exposed as a configuration or something else easily > consumable from the home.html.esp script. > There should be a small amount of logic so that we display the latest > released version, even if the starter version is a SNAPSHOT one. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-10606) Default login page should not reference content from the starter.content module
[ https://issues.apache.org/jira/browse/SLING-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman updated SLING-10606: Fix Version/s: Starter Content 1.0.16 (was: Starter Content 1.0.14) > Default login page should not reference content from the starter.content > module > --- > > Key: SLING-10606 > URL: https://issues.apache.org/jira/browse/SLING-10606 > Project: Sling > Issue Type: Improvement > Components: Authentication, Starter >Reporter: Robert Munteanu >Priority: Major > Fix For: Form Based Authentication 1.0.26, Starter Content 1.0.16 > > Attachments: login-form-without-starter-content.png, > resources-not-found-without-starter-content.png > > > The default login form references images and styles from the starter.content. > We should avoid that, since the default login form can be deployed in other > scenarios as well. Instead, we should: > - provide a standalone login page for the o.a.s.auth.form bundle > - move the current login form to o.a.s.starter.content bundle > The intent is to have a good-looking form for the starter content but also > one that does not look broken for auth.form. > We should also add an HTML comment to the default login form pointing to > customisation possibilites. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12112) Update to Sling Bundle Parent 52
Eric Norman created SLING-12112: --- Summary: Update to Sling Bundle Parent 52 Key: SLING-12112 URL: https://issues.apache.org/jira/browse/SLING-12112 Project: Sling Issue Type: Improvement Reporter: Eric Norman Assignee: Eric Norman Fix For: Starter Content 1.0.14 Update to Sling Bundle Parent 52 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-12105) Bump dependencies to the earliest versions without known vulnerabilities
[
https://issues.apache.org/jira/browse/SLING-12105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-12105.
-
Resolution: Fixed
Merged PR at:
[{{0d35fa4}}|https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-accessmanager/commit/0d35fa49b16934e7bad8736d7d49daa4e8493cfd]
> Bump dependencies to the earliest versions without known vulnerabilities
>
>
> Key: SLING-12105
> URL: https://issues.apache.org/jira/browse/SLING-12105
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: JCR Jackrabbit Access Manager 4.0.0
>
>
> Mostly to keep tooling from flagging these as "vulnerabilities from
> dependencies"
> # bump org.apache.sling.api to 2.25.4
> # bump org.apache.sling.jcr.base to 3.1.12
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (SLING-12106) Bump dependencies to the earliest versions without known vulnerabilities
[
https://issues.apache.org/jira/browse/SLING-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman resolved SLING-12106.
-
Resolution: Fixed
Merged PR at:
[{{060ca25}}|https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-usermanager/commit/060ca25a63db06d649a66b502b13afeab5ad7638]
> Bump dependencies to the earliest versions without known vulnerabilities
>
>
> Key: SLING-12106
> URL: https://issues.apache.org/jira/browse/SLING-12106
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
>Priority: Major
> Fix For: JCR Jackrabbit User Manager 2.2.28
>
>
> Mostly to keep tooling from flagging these as "vulnerabilities from
> dependencies"
> # bump org.apache.sling.servlets.post to 2.3.22
> # bump org.apache.sling.jcr.base to 3.1.12
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SLING-12106) Bump dependencies to the earliest versions without known vulnerabilities
Eric Norman created SLING-12106: --- Summary: Bump dependencies to the earliest versions without known vulnerabilities Key: SLING-12106 URL: https://issues.apache.org/jira/browse/SLING-12106 Project: Sling Issue Type: Improvement Reporter: Eric Norman Assignee: Eric Norman Fix For: JCR Jackrabbit User Manager 2.2.28 Mostly to keep tooling from flagging these as "vulnerabilities from dependencies" # bump org.apache.sling.servlets.post to 2.3.22 # bump org.apache.sling.jcr.base to 3.1.12 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12105) Bump dependencies to the earliest versions without known vulnerabilities
Eric Norman created SLING-12105: --- Summary: Bump dependencies to the earliest versions without known vulnerabilities Key: SLING-12105 URL: https://issues.apache.org/jira/browse/SLING-12105 Project: Sling Issue Type: Improvement Reporter: Eric Norman Assignee: Eric Norman Fix For: JCR Jackrabbit Access Manager 4.0.0 Mostly to keep tooling from flagging these as "vulnerabilities from dependencies" # bump org.apache.sling.api to 2.25.4 # bump org.apache.sling.jcr.base to 3.1.12 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12044) Update to Sling Bundle Parent 52
[ https://issues.apache.org/jira/browse/SLING-12044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12044. --- > Update to Sling Bundle Parent 52 > > > Key: SLING-12044 > URL: https://issues.apache.org/jira/browse/SLING-12044 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Maintenance 1.1.0 > > > Update to the latest bundle parent -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12034) bump oak dependency for compatibility with oak version 1.56.0
[ https://issues.apache.org/jira/browse/SLING-12034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12034. --- > bump oak dependency for compatibility with oak version 1.56.0 > -- > > Key: SLING-12034 > URL: https://issues.apache.org/jira/browse/SLING-12034 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Maintenance 1.1.0 > > > In order for sling to work with the latest release of oak, the oak > dependencies must be bumped to 1.56.0 or later. > The oak 1.56.0 release completed the removal of the dependency on the old > guava library which required a bump of the major version of some exported > packages whose public api has changed. The imports of those changed packages > must be bumped to the new major version number in order for the bundles to > resolve properly in the runtime. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12035) bump oak dependency for compatibility with oak version 1.56.0
[ https://issues.apache.org/jira/browse/SLING-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12035. --- > bump oak dependency for compatibility with oak version 1.56.0 > - > > Key: SLING-12035 > URL: https://issues.apache.org/jira/browse/SLING-12035 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Oak Server 1.4.0 > > > In order for sling to work with the latest release of oak, the oak > dependencies must be bumped to 1.56.0 or later. > The oak 1.56.0 release completed the removal of the dependency on the old > guava library which required a bump of the major version of some exported > packages whose public api has changed. The imports of those changed packages > must be bumped to the new major version number in order for the bundles to > resolve properly in the runtime. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11322) Reenable javadoc generation for internal packages
[ https://issues.apache.org/jira/browse/SLING-11322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-11322. --- > Reenable javadoc generation for internal packages > - > > Key: SLING-11322 > URL: https://issues.apache.org/jira/browse/SLING-11322 > Project: Sling > Issue Type: Task > Components: JCR, Oak >Affects Versions: JCR Oak Server 1.2.10 >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Minor > Fix For: JCR Oak Server 1.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11474) Update Testing PaxExam to 4.0.0
[ https://issues.apache.org/jira/browse/SLING-11474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-11474. --- > Update Testing PaxExam to 4.0.0 > --- > > Key: SLING-11474 > URL: https://issues.apache.org/jira/browse/SLING-11474 > Project: Sling > Issue Type: Sub-task > Components: JCR, Oak >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > Fix For: JCR Oak Server 1.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12045) Update to Sling Bundle Parent 52
[ https://issues.apache.org/jira/browse/SLING-12045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-12045. --- > Update to Sling Bundle Parent 52 > > > Key: SLING-12045 > URL: https://issues.apache.org/jira/browse/SLING-12045 > Project: Sling > Issue Type: Improvement > Reporter: Eric Norman > Assignee: Eric Norman >Priority: Major > Fix For: JCR Oak Server 1.4.0 > > > Update to latest bundle parent version -- This message was sent by Atlassian Jira (v8.20.10#820010)
