[
https://issues.apache.org/jira/browse/SLING-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281303#comment-17281303
]
Stefan Egli commented on SLING-10120:
-------------------------------------
* started work on parent 40 switch see [this
PR|https://github.com/apache/sling-org-apache-sling-event/pull/10]
* the problem currently with that PR is that it still doesn't work with java11
for ITs (unit tests are fine) : it complains about missing osgi.ee
dependencies.. eg:
{noformat}
[ERROR] org.apache.sling.event.it.HistoryTest.testHistory Time elapsed: 1.262
s <<< ERROR!
org.osgi.framework.BundleException: Unable to resolve
PAXExamConfigurationOption-3e39ca0b-c1d6-4556-a0f1-adde7a0537ee [180](R 180.0):
missing requirement
[PAXExamConfigurationOption-3e39ca0b-c1d6-4556-a0f1-adde7a0537ee [180](R
180.0)] osgi.wiring.package; (osgi.wiring.package=org.slf4j) [caused by: Unable
to resolve slf4j.api [26](R 26.0): missing requirement [slf4j.api [26](R 26.0)]
osgi.ee; (&(osgi.ee=JavaSE)(version=1.5.0))] Unresolved requirements:
[[PAXExamConfigurationOption-3e39ca0b-c1d6-4556-a0f1-adde7a0537ee [180](R
180.0)] osgi.wiring.package; (osgi.wiring.package=org.slf4j)]
at
org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4132)
{noformat}
* I started upgrading the outdated bundle versions in AbstractJobHandlingTest
but think that might be more work - as updating versions there requires a full
functioning set of versions
I'm wondering if we should go ahead with above PR and do a new vote on that to
get sling.event 4.2.16 out - or if we should also include java11 support for
ITs ..
Also open for any input.
/cc [~rombert], [~karlpauls]
> Upgrade event to parent 40
> --------------------------
>
> Key: SLING-10120
> URL: https://issues.apache.org/jira/browse/SLING-10120
> Project: Sling
> Issue Type: Sub-task
> Components: Event
> Reporter: Robert Munteanu
> Assignee: Stefan Egli
> Priority: Major
> Fix For: Event 4.2.16
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
