I don't know much about sling models caching, but it seems storing the
cache into the resource resolver and therefore binding it to that
lifecycle sounds very reasonable to me. And due to the mentioned support
for Closeable, the cache gets discarded automatically with the resolver
being
+1
Carsten
On 29.01.2024 13:37, 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
+1
stefan
On Mon, 2024-01-29 at 12:37 +, Robert Munteanu wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
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
[
https://issues.apache.org/jira/browse/SLING-12234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-12234:
Fix Version/s: Commons Log 5.5.2
(was: Commons Log 5.5.0)
>
[
https://issues.apache.org/jira/browse/SLING-12240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu reopened SLING-12240:
-
> Upgrade to parent pom 52 and Java 11
>
>
>
[
https://issues.apache.org/jira/browse/SLING-12240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-12240.
-
Resolution: Fixed
> Upgrade to parent pom 52 and Java 11
>
