[jira] [Created] (SLING-12240) Upgrade to parent pom 52 and Java 11

2024-01-24 Thread Robert Munteanu (Jira)
Robert Munteanu created SLING-12240:
---

 Summary: Upgrade to parent pom 52 and Java 11
 Key: SLING-12240
 URL: https://issues.apache.org/jira/browse/SLING-12240
 Project: Sling
  Issue Type: Improvement
Reporter: Robert Munteanu
Assignee: Robert Munteanu
 Fix For: Commons Log 5.4.4


This way we can take advantage of the latest improvements.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


Re: [PR] Update to Java 11 and the latest parent pom [sling-org-apache-sling-commons-log]

2024-01-24 Thread via GitHub


rombert merged PR #17:
URL: https://github.com/apache/sling-org-apache-sling-commons-log/pull/17


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] chore(deps): update dependency org.slf4j:slf4j-api to v2 [sling-org-apache-sling-starter]

2024-01-24 Thread via GitHub


renovate-bot opened a new pull request, #301:
URL: https://github.com/apache/sling-org-apache-sling-starter/pull/301

   [![Mend 
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)
   
   This PR contains the following updates:
   
   | Package | Change | Age | Adoption | Passing | Confidence |
   |---|---|---|---|---|---|
   | [org.slf4j:slf4j-api](http://www.slf4j.org) 
([source](https://togithub.com/qos-ch/slf4j)) | `1.7.36` -> `2.0.11` | 
[![age](https://developer.mend.io/api/mc/badges/age/maven/org.slf4j:slf4j-api/2.0.11?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 | 
[![adoption](https://developer.mend.io/api/mc/badges/adoption/maven/org.slf4j:slf4j-api/2.0.11?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 | 
[![passing](https://developer.mend.io/api/mc/badges/compatibility/maven/org.slf4j:slf4j-api/1.7.36/2.0.11?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 | 
[![confidence](https://developer.mend.io/api/mc/badges/confidence/maven/org.slf4j:slf4j-api/1.7.36/2.0.11?slim=true)](https://docs.renovatebot.com/merge-confidence/)
 |
   
   ---
   
   ### Release Notes
   
   
   qos-ch/slf4j (org.slf4j:slf4j-api)
   
   ### 
[`v2.0.11`](https://togithub.com/qos-ch/slf4j/compare/v_2.0.10...v_2.0.11)
   
   ### [`v2.0.10`](https://togithub.com/qos-ch/slf4j/compare/v_2.0.9...v_2.0.10)
   
   ### [`v2.0.9`](https://togithub.com/qos-ch/slf4j/compare/v_2.0.8...v_2.0.9)
   
   ### [`v2.0.8`](https://togithub.com/qos-ch/slf4j/compare/v_2.0.7...v_2.0.8)
   
   ### [`v2.0.7`](https://togithub.com/qos-ch/slf4j/compare/v_2.0.6...v_2.0.7)
   
   ### [`v2.0.6`](https://togithub.com/qos-ch/slf4j/compare/v_2.0.5...v_2.0.6)
   
   ### [`v2.0.5`](https://togithub.com/qos-ch/slf4j/compare/v_2.0.4...v_2.0.5)
   
   ### [`v2.0.4`](https://togithub.com/qos-ch/slf4j/compare/v_2.0.3...v_2.0.4)
   
   ### [`v2.0.3`](https://togithub.com/qos-ch/slf4j/compare/v_2.0.2...v_2.0.3)
   
   ### [`v2.0.2`](https://togithub.com/qos-ch/slf4j/compare/v_2.0.1...v_2.0.2)
   
   ### [`v2.0.1`](https://togithub.com/qos-ch/slf4j/compare/v_2.0.0...v_2.0.1)
   
   ### [`v2.0.0`](https://togithub.com/qos-ch/slf4j/compare/v_1.7.36...v_2.0.0)
   
   
   
   ---
   
   ### Configuration
   
    **Schedule**: Branch creation - At any time (no schedule defined), 
Automerge - At any time (no schedule defined).
   
    **Automerge**: Disabled by config. Please merge this manually once you are 
satisfied.
   
   ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry 
checkbox.
   
    **Ignore**: Close this PR and you won't be reminded about this update 
again.
   
   ---
   
- [ ] If you want to rebase/retry this PR, check this 
box
   
   ---
   
   This PR has been generated by [Mend 
Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository 
job log 
[here](https://developer.mend.io/github/apache/sling-org-apache-sling-starter).
   

   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] chore(deps): update dependency org.apache.sling:org.apache.sling.installer.core to v3.14.0 [sling-org-apache-sling-starter]

2024-01-24 Thread via GitHub


rombert merged PR #300:
URL: https://github.com/apache/sling-org-apache-sling-starter/pull/300


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[VOTE] Release Apache Sling Servlets Resolver 2.11.0

2024-01-24 Thread Carsten Ziegeler

Hi,

We solved 1 issues in this release
https://issues.apache.org/jira/browse/SLING-12233


Staging repository: 
https://repository.apache.org/content/repositories/orgapachesling-2834/


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 2834 /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


Re: [PR] chore(deps): update dependency org.apache.felix:org.apache.felix.scr to v2.2.10 [sling-org-apache-sling-starter]

2024-01-24 Thread via GitHub


rombert merged PR #297:
URL: https://github.com/apache/sling-org-apache-sling-starter/pull/297


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [VOTE] Release Apache Sling Rewriter 1.3.10

2024-01-24 Thread Robert Munteanu
On Wed, 2024-01-24 at 07:07 +0100, Carsten Ziegeler wrote:
> Please vote to approve this release:

+1
Robert


signature.asc
Description: This is a digitally signed message part


[PR] Update to Java 11 and the latest parent pom [sling-org-apache-sling-commons-log]

2024-01-24 Thread via GitHub


rombert opened a new pull request, #17:
URL: https://github.com/apache/sling-org-apache-sling-commons-log/pull/17

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Update to Java 11 and the latest parent pom [sling-org-apache-sling-commons-log]

2024-01-24 Thread via GitHub


sonarcloud[bot] commented on PR #17:
URL: 
https://github.com/apache/sling-org-apache-sling-commons-log/pull/17#issuecomment-1908258259

   ## [![Quality Gate 
Passed](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/QualityGateBadge/qg-passed-20px.png
 'Quality Gate 
Passed')](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-commons-log=17)
 **Quality Gate passed**  
   Kudos, no new issues were introduced!
   
   [0 New 
issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-commons-log=17=false=true)
  
   [0 Security 
Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-commons-log=17=false=true)
  
   No data about Coverage  
   [0.0% Duplication on New 
Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-commons-log=17=new_duplicated_lines_density=list)
  
 
   [See analysis details on 
SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-commons-log=17)
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



RE: [VOTE] Release Apache Sling Servlets Resolver 2.11.0

2024-01-24 Thread Stefan Seifert
+1

stefan 


RE: [VOTE] Release Apache Sling Rewriter 1.3.10

2024-01-24 Thread Stefan Seifert
+1

stefan 


[jira] [Commented] (SLING-11906) Migrate to slf4j 2.x

2024-01-24 Thread Konrad Windszus (Jira)


[ 
https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17810474#comment-17810474
 ] 

Konrad Windszus commented on SLING-11906:
-

The fix in SLF4J 2.0.11 only exports {{org.slf4j.helpers}} in a backwards 
compatible way. I think we should get rid of imports towards {{org.sl4j.event}} 
as that was IMHO never devised as stable API (but only supposed to be used 
internally).

> 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
>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)


[jira] [Comment Edited] (SLING-11906) Migrate to slf4j 2.x

2024-01-24 Thread Konrad Windszus (Jira)


[ 
https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17810474#comment-17810474
 ] 

Konrad Windszus edited comment on SLING-11906 at 1/24/24 3:57 PM:
--

The fix in SLF4J 2.0.11 only exports {{org.slf4j.helpers}} in a backwards 
compatible way 
(https://github.com/qos-ch/slf4j/commit/02b36a269a9b13dac435699839f3200529dd0e10).
 I think we should get rid of imports towards {{org.sl4j.event}} as that was 
IMHO never devised as stable API (but only supposed to be used internally).


was (Author: kwin):
The fix in SLF4J 2.0.11 only exports {{org.slf4j.helpers}} in a backwards 
compatible way. I think we should get rid of imports towards {{org.sl4j.event}} 
as that was IMHO never devised as stable API (but only supposed to be used 
internally).

> 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
>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)


[jira] [Commented] (SLING-11906) Migrate to slf4j 2.x

2024-01-24 Thread Robert Munteanu (Jira)


[ 
https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17810482#comment-17810482
 ] 

Robert Munteanu commented on SLING-11906:
-

[~kwin] - perhaps upgrading logback to 1.3.x. or 1.4.x in Commons Log will 
remove the need to import the old package; did not have the time to investigate.

> 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
>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)


[jira] [Commented] (SLING-11906) Migrate to slf4j 2.x

2024-01-24 Thread Julian Reschke (Jira)


[ 
https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17810479#comment-17810479
 ] 

Julian Reschke commented on SLING-11906:


Awesome. Thanks.

> 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
>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: [VOTE] Release Apache Sling Servlets Resolver 2.11.0

2024-01-24 Thread Robert Munteanu
On Wed, 2024-01-24 at 14:56 +0100, Carsten Ziegeler wrote:
> Please vote to approve this release:

+1
Robert


signature.asc
Description: This is a digitally signed message part


[jira] [Commented] (SLING-11906) Migrate to slf4j 2.x

2024-01-24 Thread Robert Munteanu (Jira)


[ 
https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17810441#comment-17810441
 ] 

Robert Munteanu commented on SLING-11906:
-

For the record, when trying to upgrade to slf4j 2.0.11 the following errors 
come up

- Oak bundles importing org.slf4j.event with narrow range
- Sling commons.log importing org.slf4j.event with narrow range
- missing serviceloader mediator capability

{noformat}
[ERROR] [bundle-packages] org.apache.jackrabbit:oak-lucene:1.60.0: Bundle is 
importing package org.slf4j.event;version=[1.7,2) with start order 15 but no 
bundle is exporting these for that start order in the required version range.
[ERROR] [bundle-packages] org.apache.jackrabbit:oak-store-document:1.60.0: 
Bundle is importing package org.slf4j.event;version=[1.7,2) with start order 15 
but no bundle is exporting these for that start order in the required version 
range.
[ERROR] [bundle-packages] org.apache.sling:org.apache.sling.commons.log:5.4.2: 
Bundle is importing packages [Package org.slf4j.event;version=[1.7,2), Package 
org.slf4j.spi;version=[1.7,2)] with start order 1 but no bundle is exporting 
these for that start order in the required version range.
[ERROR] [bundle-packages] org.apache.jackrabbit:oak-commons:1.60.0: Bundle is 
importing package org.slf4j.event;version=[1.7,2) with start order 15 but no 
bundle is exporting these for that start order in the required version range.
[ERROR] [bundle-packages] org.apache.jackrabbit:oak-core:1.60.0: Bundle is 
importing package org.slf4j.event;version=[1.7,2) with start order 15 but no 
bundle is exporting these for that start order in the required version range.
[ERROR] [bundle-packages] org.apache.jackrabbit:oak-query-spi:1.60.0: Bundle is 
importing package org.slf4j.event;version=[1.7,2) with start order 15 but no 
bundle is exporting these for that start order in the required version range.
[ERROR] [requirements-capabilities] org.slf4j:slf4j-api:2.0.11: Artifact 
org.slf4j:slf4j-api:2.0.11 requires [slf4j.api/2.0.11] osgi.serviceloader; 
osgi.serviceloader=org.slf4j.spi.SLF4JServiceProvider; 
filter:="(osgi.serviceloader=org.slf4j.spi.SLF4JServiceProvider)" in start 
level 1 but no artifact is providing a matching capability in this start level.
{noformat}

> 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
>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)


[jira] [Commented] (SLING-11906) Migrate to slf4j 2.x

2024-01-24 Thread Julian Reschke (Jira)


[ 
https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17810475#comment-17810475
 ] 

Julian Reschke commented on SLING-11906:


[~kwin] - IIUC, Oak has similar problems wrt using SLF packages it should not? 
Could you open an issue over there once we fully understand what needs to be 
done?

> 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
>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)


[jira] [Comment Edited] (SLING-11906) Migrate to slf4j 2.x

2024-01-24 Thread Robert Munteanu (Jira)


[ 
https://issues.apache.org/jira/browse/SLING-11906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17810441#comment-17810441
 ] 

Robert Munteanu edited comment on SLING-11906 at 1/24/24 3:45 PM:
--

For the record, when trying to upgrade to slf4j 2.0.11 the following errors 
come up

- Oak bundles importing org.slf4j.event with narrow range
- Sling commons.log importing org.slf4j.event with narrow range
- missing serviceloader mediator capability

{noformat}
[ERROR] [bundle-packages] org.apache.jackrabbit:oak-lucene:1.60.0: Bundle is 
importing package org.slf4j.event;version=[1.7,2) with start order 15 but no 
bundle is exporting these for that start order in the required version range.
[ERROR] [bundle-packages] org.apache.jackrabbit:oak-store-document:1.60.0: 
Bundle is importing package org.slf4j.event;version=[1.7,2) with start order 15 
but no bundle is exporting these for that start order in the required version 
range.
[ERROR] [bundle-packages] org.apache.sling:org.apache.sling.commons.log:5.4.2: 
Bundle is importing packages [Package org.slf4j.event;version=[1.7,2), Package 
org.slf4j.spi;version=[1.7,2)] with start order 1 but no bundle is exporting 
these for that start order in the required version range.
[ERROR] [bundle-packages] org.apache.jackrabbit:oak-commons:1.60.0: Bundle is 
importing package org.slf4j.event;version=[1.7,2) with start order 15 but no 
bundle is exporting these for that start order in the required version range.
[ERROR] [bundle-packages] org.apache.jackrabbit:oak-core:1.60.0: Bundle is 
importing package org.slf4j.event;version=[1.7,2) with start order 15 but no 
bundle is exporting these for that start order in the required version range.
[ERROR] [bundle-packages] org.apache.jackrabbit:oak-query-spi:1.60.0: Bundle is 
importing package org.slf4j.event;version=[1.7,2) with start order 15 but no 
bundle is exporting these for that start order in the required version range.
[ERROR] [requirements-capabilities] org.slf4j:slf4j-api:2.0.11: Artifact 
org.slf4j:slf4j-api:2.0.11 requires [slf4j.api/2.0.11] osgi.serviceloader; 
osgi.serviceloader=org.slf4j.spi.SLF4JServiceProvider; 
filter:="(osgi.serviceloader=org.slf4j.spi.SLF4JServiceProvider)" in start 
level 1 but no artifact is providing a matching capability in this start level.
{noformat}

-

Edit: the commons.log import is probably coming from the ch.qos.logback.classic 
packages that we wrap and re-export.


was (Author: rombert):
For the record, when trying to upgrade to slf4j 2.0.11 the following errors 
come up

- Oak bundles importing org.slf4j.event with narrow range
- Sling commons.log importing org.slf4j.event with narrow range
- missing serviceloader mediator capability

{noformat}
[ERROR] [bundle-packages] org.apache.jackrabbit:oak-lucene:1.60.0: Bundle is 
importing package org.slf4j.event;version=[1.7,2) with start order 15 but no 
bundle is exporting these for that start order in the required version range.
[ERROR] [bundle-packages] org.apache.jackrabbit:oak-store-document:1.60.0: 
Bundle is importing package org.slf4j.event;version=[1.7,2) with start order 15 
but no bundle is exporting these for that start order in the required version 
range.
[ERROR] [bundle-packages] org.apache.sling:org.apache.sling.commons.log:5.4.2: 
Bundle is importing packages [Package org.slf4j.event;version=[1.7,2), Package 
org.slf4j.spi;version=[1.7,2)] with start order 1 but no bundle is exporting 
these for that start order in the required version range.
[ERROR] [bundle-packages] org.apache.jackrabbit:oak-commons:1.60.0: Bundle is 
importing package org.slf4j.event;version=[1.7,2) with start order 15 but no 
bundle is exporting these for that start order in the required version range.
[ERROR] [bundle-packages] org.apache.jackrabbit:oak-core:1.60.0: Bundle is 
importing package org.slf4j.event;version=[1.7,2) with start order 15 but no 
bundle is exporting these for that start order in the required version range.
[ERROR] [bundle-packages] org.apache.jackrabbit:oak-query-spi:1.60.0: Bundle is 
importing package org.slf4j.event;version=[1.7,2) with start order 15 but no 
bundle is exporting these for that start order in the required version range.
[ERROR] [requirements-capabilities] org.slf4j:slf4j-api:2.0.11: Artifact 
org.slf4j:slf4j-api:2.0.11 requires [slf4j.api/2.0.11] osgi.serviceloader; 
osgi.serviceloader=org.slf4j.spi.SLF4JServiceProvider; 
filter:="(osgi.serviceloader=org.slf4j.spi.SLF4JServiceProvider)" in start 
level 1 but no artifact is providing a matching capability in this start level.
{noformat}

> 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
>Priority: Major
> Fix For: Commons Log 6.0.0

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

2024-01-24 Thread Eric Norman
+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
>