[
https://issues.apache.org/jira/browse/SLING-7522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16380532#comment-16380532
]
Oliver Lietz commented on SLING-7522:
-------------------------------------
Everything is fine with Commons Scheduler and Karaf, see feature
[sling-commons-scheduler|https://github.com/apache/sling-org-apache-sling-karaf-features/blob/master/src/main/feature/feature.xml#L115]:
{noformat}
<feature name="sling-commons-scheduler" version="${project.version}">
<bundle>mvn:org.apache.sling/org.apache.sling.commons.scheduler/2.7.2</bundle>
<!-- dependencies -->
<feature>scr</feature>
<feature version="${project.version}">sling-commons-threads</feature>
<bundle dependency="true">mvn:javax.servlet/javax.servlet-api/3.1.0</bundle>
<bundle
dependency="true">mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/1.1.1</bundle>
<bundle
dependency="true">mvn:io.dropwizard.metrics/metrics-core/3.2.6</bundle>
</feature>
{noformat}
> Scheduler bundle/package version mismatch
> -----------------------------------------
>
> Key: SLING-7522
> URL: https://issues.apache.org/jira/browse/SLING-7522
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons Scheduler 2.7.2
> Reporter: Amichai Rothman
> Priority: Major
>
> I just tried to upgrade from scheduler 2.5.2 to 2.7.2, and it did not go
> smooth.
> First, there appears to be a new dependency on
> org.apache.sling.commons.metrics and io.dropwizard.metrics, which I didn't
> see documented anywhere, but ok.
> More importantly, the scheduler bundle version (and maven dependency version
> I specified) is 2.7.2, but the packages exported (and imported back) by the
> bundle is org.apache.sling.commons.scheduler;version=2.5.1. This version
> mismatch seems to confuse karaf, which is expecting to find 2.7.2 but
> doesn't, so my feature does not resolve. While there's a chance this is a bug
> in Karaf or there is some sort of workaround in generating the feature, the
> version mismatch does seem strange and a likely bug in the scheduler as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
