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

Oliver Lietz edited comment on SLING-11143 at 2/16/22, 7:58 PM:
----------------------------------------------------------------

By adding a single line ({{\-jpms-module-info:}}) to {{bnd.bnd}} for Commons 
Threads we create a {{module-info.class}} with proper module name. Adding a 
configuration for -failsafe- surefire will also make the tests working on Java 
17 ({{\--add-opens java.base/java.lang=org.apache.sling.commons.threads}}).


was (Author: olli):
By adding a single line ({{{}-jpms-module-info:{}}}) to {{bnd.bnd}} for Commons 
Threads we create a {{module-info.class}} with proper module name. Adding a 
configuration for -failsafe- surefire will also make the tests working on Java 
17 ({{{}--add-opens java.base/java.lang=org.apache.sling.commons.threads{}}}).

> Work around SLING-10831 by adding an add-opens flag to the Starter entrypoint
> -----------------------------------------------------------------------------
>
>                 Key: SLING-11143
>                 URL: https://issues.apache.org/jira/browse/SLING-11143
>             Project: Sling
>          Issue Type: Sub-task
>          Components: Starter
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Major
>             Fix For: Starter 12
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Until we get SLING-10831 properly fixed we should ensure that the Docker 
> image does not print the error by default.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to